chia-blockchain tokens can be inflated to an arbitrary extent

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2022-36447: 0.86% estimated exploitation activity in the next 30 days; percentile 58.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

An inflation issue was discovered in Chia Network CAT1 Standard 1.0.0. Previously minted tokens minted on the Chia blockchain using the CAT1 standard can be inflated to an arbitrary extent by any holder of any amount of the token. The total amount of the token can be increased as high as the malicious actor pleases. This is true for every CAT1 on the Chia blockchain regardless of issuance rules. This attack is auditable on chain, so maliciously altered coins can potentially be marked by off-chain observers as malicious.

Published by the source

30 Jul 2022, 00:00 UTC

Last modified by the source

2 Dec 2024, 05:40 UTC

Source last checked

26 Oct 2026, 13:27 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-pvjg-jwp3-mrj5

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-pvjg-jwp3-mrj5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-36447

Advisory: chia-blockchain tokens can be inflated to an arbitrary extent
IDs: CVE-2022-36447, GHSA-pvjg-jwp3-mrj5
Record: https://patchnext.com/advisories/cve-2022-36447 (revision 2, source checked 26 Oct 2026, 13:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI chia-blockchain: affected <= 2.4.4rc3

## Suggested inspection (read-only)
- `python -m pip show chia-blockchain`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on chia-blockchain.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-pvjg-jwp3-mrj5 (OSV record GHSA-pvjg-jwp3-mrj5 lists affected ranges: PyPI chia-blockchain >=0 <=2.4.4rc3)
- Verified: https://github.com/advisories/GHSA-pvjg-jwp3-mrj5 (GitHub-reviewed advisory GHSA-pvjg-jwp3-mrj5 lists affected ranges: PyPI chia-blockchain >=0 <=2.4.4rc3)

Commands are suggestions: review each one before running it.