stleary JSON-java up to 20260522 JSONObject.java allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 3.03+ |
Summary
A vulnerability, which was classified as problematic, has been found in stleary JSON-java up to 20260522. Affected by this vulnerability is an unknown functionality of the file src/main/java/org/json/JSONObject.java. This manipulation causes allocation of resources. This vulnerability is registered as CVE-2026-59171. Remote exploitation of the attack is possible. Furthermore, an exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in stleary JSON-java up to 20260522. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file src/main/java/org/json/JSONObject.java. The manipulation with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-59171. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1499 for this issue.
It is possible to download the exploit at github.com. It is declared as proof-of-concept.
Upgrading to version 20260719 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 1efb5f6c4303fbc173697852654088de1ed2b0a3 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.7
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: JSON-java 20260719
Patch: 1efb5f6c4303fbc173697852654088de1ed2b0a3
Timeline
08/06/2026 Advisory disclosed08/06/2026 VulDB entry created
08/06/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 758
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-59171 (🔒)
GCVE (CVE): GCVE-0-2026-59171
GCVE (VulDB): GCVE-100-386485
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/06/2026 09:22Changes: 08/06/2026 09:22 (62)
Complete: 🔍
Submitter: Wayde.Shi24
Cache ID: 216::103
Submit
Accepted
- Submit #863098: org.json JSON-java <= 20260522 Uncontrolled Resource Consumption, Allocation of Resources Witho (by Wayde.Shi24)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.