How severe is GHSA-hx9q-6w63-j58v?

No CVSS score has been assigned to GHSA-hx9q-6w63-j58v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hx9q-6w63-j58v?

GHSA-hx9q-6w63-j58v affects the following packages: orjson (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-hx9q-6w63-j58v?

Update orjson to 3.11.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hx9q-6w63-j58v is resolved across your whole dependency graph.

How do I detect GHSA-hx9q-6w63-j58v in my PyPI dependencies?

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

How do I mitigate GHSA-hx9q-6w63-j58v 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-hx9q-6w63-j58v?

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

Is GHSA-hx9q-6w63-j58v actively exploited in the wild?

No public exploit code has been indexed for GHSA-hx9q-6w63-j58v 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-hx9q-6w63-j58v?

GHSA-hx9q-6w63-j58v has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th 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.

What type of vulnerability is GHSA-hx9q-6w63-j58v?

GHSA-hx9q-6w63-j58v is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hx9q-6w63-j58v published, and has it been updated?

GHSA-hx9q-6w63-j58v was published on January 22, 2026 and was last updated on September 10, 2026. 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

GHSA-hx9q-6w63-j58v — orjson

Fix: ijl/orjson@62bb185

GHSA-hx9q-6w63-j58v is a CWE-770 vulnerability in orjson. A fix is available for orjson — see the affected versions and patch details below.

orjson does not limit recursion for deeply nested JSON documents

Also known asCVE-2025-67221PYSEC-2026-107

Published

Jan 22, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hx9q-6w63-j58v.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% 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.

Real-World Exposure

1 pkg affected

🐍orjson

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

The orjson.dumps function in orjson before 3.11.6 does not limit recursion for deeply nested JSON documents.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`orjson`	all versions	3.11.6`pip install --upgrade 'orjson==3.11.6'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for orjson, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update orjson to 3.11.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hx9q-6w63-j58v is resolved across your whole dependency graph.
Workarounds
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-hx9q-6w63-j58v can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hx9q-6w63-j58v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The orjson.dumps function in orjson before 3.11.6 does not limit recursion for deeply nested JSON documents.

O3 Security · Impact-Aware SCA

Is GHSA-hx9q-6w63-j58v in your dependencies?

O3 Security finds GHSA-hx9q-6w63-j58v 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