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.
References
Configurations
No configuration.
History
02 Jul 2026, 13:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/444 - |
02 Jul 2026, 09:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-07-02 09:16
Updated : 2026-07-02 17:44
NVD link : CVE-2026-9563
Mitre link : CVE-2026-9563
CVE.ORG link : CVE-2026-9563
JSON object : View
Products Affected
No product.
