PT-2026-54936 · Eclipse Foundation · Eclipse Parsson

Mark Swatosh · Published 2026-07-02 · Updated 2026-07-02 · CVE-2026-9563

NVD

CVSS v3.1

7.5

High

Base vector

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

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.

Fix

Allocation of Resources Without Limits

Resource Exhaustion

Weakness Enumeration

CWE-770

CWE-400

Related Identifiers

CVE-2026-9563

Affected Products

Eclipse Parsson

References · 6

• https://nvd.nist.gov/vuln/detail/CVE-2026-9563 · Security Note
• https://github.com/eclipse-ee4j/parsson/commit/134e8d101aa74c8b9302d0cb62f6ccb4912a9d0c · Note
• https://github.com/eclipse-ee4j/parsson/tree/1.1.8 · Note
• https://github.com/eclipse-ee4j/parsson/pull/169 · Note
• https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/444 · Note
• https://repo.maven.apache.org/maven2/org/eclipse/parsson/parsson/1.1.8 · Note