Allocation of Resources Without Limits or Throttling Affecting org.json:json package, versions [20150729,20260719)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGJSON-22389193
- published10 Nov 2026
- disclosed9 Nov 2026
- creditwaydeshi
Introduced: 9 Nov 2026
NewCVE-2026-59171 (opens in a new tab)How to fix?
Upgrade org.json:json to version 20260719 or higher.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via numeric conversion in the JSONObject.stringToValue() and XML.stringToValue() methods. An attacker can send JSON or XML containing an extremely long numeric literal to an application that parses attacker-controlled input with org.json; constructing a BigInteger or BigDecimal from it consumes excessive CPU and blocks request-handling threads, causing legitimate requests to time out.
Workarounds
- Set nginx’s
client_max_body_size 64k;to limit request bodies and reduce the maximum size of numeric literals reaching the parser. - In Spring Boot, register a
CommonsRequestLoggingFilterorOncePerRequestFilterthat capsContent-Lengthbefore the request reaches the controller, limiting the size of inputs the parser processes.