NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

orjson does not limit recursion for deeply nested JSON documentsGHSA-pwr2-4v36-6qpr

HIGHFix: ijl/orjson@b0e4d2c

GHSA-pwr2-4v36-6qpr is a high-severity (CVSS 7.5) CWE-674 vulnerability in orjson. A fix is available for orjson — see the affected versions and patch details below.

Also known asCVE-2024-27454PYSEC-2024-40
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-pwr2-4v36-6qpr.

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk-0.01%
Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk
0.00%0.57%1.13%1.70%0.1%1.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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

orjson.loads in orjson before 3.9.15 does not limit recursion for deeply nested JSON documents.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIorjsonall versions3.9.15pip install --upgrade 'orjson==3.9.15'

Affected Products

1 product · 1 configurations
Application
orjsonijl
< 3.9.15
range

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update orjson to 3.9.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pwr2-4v36-6qpr is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

orjson.loads in orjson before 3.9.15 does not limit recursion for deeply nested JSON documents.
O3 Security · Impact-Aware SCA

Is GHSA-pwr2-4v36-6qpr in your dependencies?

Find it across PyPI, including transitive dependencies.

orjson does not limit recursion for deeply nested JSON…