CVE-2026-9563

In Eclipse Parsson published Maven Central artifacts before version 1.1.8, the JSON parser did not enforce a default maximum on the number of characters consumed while parsing a single JSON document. Applications that parse attacker- controlled JSON can be forced to consume excessive CPU and memory by processing very large documents, including large arrays, objects, strings, numbers, whitespace, or nested structures, resulting in a denial of service. Eclipse Parsson 1.1.8 introduces a configurable maximum parsing limit with a default limit of 15 million parser-consumed characters.

CVSS 3.1

7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

0.3% chance of exploitation in the next 30 days; higher than 27% of CVEs (scores of 2026-10-25)

CWEs

CWE-400, CWE-770

Published

2026-07-02

Modified

2026-10-25

Record from

the NVD, synced 2026-10-25

References

• https://github.com/eclipse-ee4j/parsson/commit/134e8d101aa74c8b9302d0cb62f6ccb4912a9d0c
• https://github.com/eclipse-ee4j/parsson/pull/169
• https://github.com/eclipse-ee4j/parsson/tree/1.1.8
• https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/444
• https://repo.maven.apache.org/maven2/org/eclipse/parsson/parsson/1.1.8/

Check your stackJSON