CVE-2026-9563
In Eclipse Parsson published Maven Central artifacts before version …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/eclipse-ee4j/parsson/commit/134e8d101aa74c8b9302d0cb62f6ccb4912a9d0c
- github.com/eclipse-ee4j/parsson/pull/169
- github.com/eclipse-ee4j/parsson/tree/1.1.8
- gitlab.eclipse.org/security/vulnerability-reports/-/work_items/444
- repo.maven.apache.org/maven2/org/eclipse/parsson/parsson/1.1.8/
- nvd.nist.gov/vuln/detail/CVE-2026-9563
- cve.org/CVERecord?id=CVE-2026-9563
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.