Description
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.
References6
- github.com/eclipse-ee4j/parsson/commit/134e8d101aa74c8b9302d0cb…
- github.com/eclipse-ee4j/parsson/pull/169
- github.com/eclipse-ee4j/parsson/tree/1.1.8
- gitlab.eclipse.org/security/vulnerability-reports/-/work_items/…
- repo.maven.apache.org/maven2/org/eclipse/parsson/parsson/1.1.8/
- gitlab.eclipse.org/security/vulnerability-reports/-/work_items/…
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 29 · as of 16 November 2026
- CWE
- CWE-400CWE-770
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.