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.
Metrics
Affected Vendors & Products
References
History
Thu, 02 Jul 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Eclipse Parsson Denial of Service via Unbounded JSON Parsing |
Thu, 02 Jul 2026 10:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eclipse
Eclipse parsson |
|
| Vendors & Products |
Eclipse
Eclipse parsson |
Thu, 02 Jul 2026 08:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Weaknesses | CWE-400 CWE-770 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: eclipse
Published:
Updated: 2026-07-02T12:27:25.923Z
Reserved: 2026-05-26T10:34:17.499Z
Link: CVE-2026-9563
No data.
No data.
No data.
OpenCVE Enrichment
Updated: 2026-07-02T15:45:16Z