How severe is GHSA-pvjg-jwp3-mrj5?

GHSA-pvjg-jwp3-mrj5 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-pvjg-jwp3-mrj5?

GHSA-pvjg-jwp3-mrj5 affects the following packages: chia-blockchain (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-pvjg-jwp3-mrj5?

No patched version of chia-blockchain has shipped for GHSA-pvjg-jwp3-mrj5 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-pvjg-jwp3-mrj5 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for chia-blockchain, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pvjg-jwp3-mrj5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-pvjg-jwp3-mrj5?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pvjg-jwp3-mrj5 can be triaged on real exposure rather than presence alone.

Is GHSA-pvjg-jwp3-mrj5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pvjg-jwp3-mrj5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-pvjg-jwp3-mrj5?

GHSA-pvjg-jwp3-mrj5 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-pvjg-jwp3-mrj5 published, and has it been updated?

GHSA-pvjg-jwp3-mrj5 was published on July 30, 2022 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

GHSA-pvjg-jwp3-mrj5 — chia-blockchain

HIGH

GHSA-pvjg-jwp3-mrj5 is a high-severity (CVSS 7.5) vulnerability in chia-blockchain. No vendor fix is recorded yet; mitigation options are listed below.

chia-blockchain tokens can be inflated to an arbitrary extent

Also known asCVE-2022-36447PYSEC-2022-43072

Published

Jul 30, 2022

Updated

Dec 2, 2024

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-pvjg-jwp3-mrj5 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

🐍chia-blockchain

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`chia-blockchain`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for chia-blockchain, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of chia-blockchain has shipped for GHSA-pvjg-jwp3-mrj5 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pvjg-jwp3-mrj5 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pvjg-jwp3-mrj5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-pvjg-jwp3-mrj5 in your dependencies?

O3 Security finds GHSA-pvjg-jwp3-mrj5 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works