CVE-2026-9563

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-02. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
27.1%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 2, 2026

Advisory Details (5)

Auto-updated Jul 2, 2026
Patch available. Sources: github_commit, github_pr.
generic

Central Repository: org/eclipse/parsson/parsson/1.1.8

https://repo.maven.apache.org/maven2/org/eclipse/parsson/parsson/1.1.8/
generic

[Eclipse Parsson] DoS vulnerability (#444) · Issues · Eclipse Projects Security / vulnerability-reports · GitLab

https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/444
generic

GitHub - eclipse-ee4j/parsson at 1.1.8 · GitHub

https://github.com/eclipse-ee4j/parsson/tree/1.1.8
github_pr Patch Available

json input size limit

Patch available: eclipse-ee4j/parsson 1.1.9 (PR #169 merged 2026-05-25)

https://github.com/eclipse-ee4j/parsson/pull/169
github_commit Patch Available

commit 134e8d101aa7 (eclipse-ee4j/parsson)

Patch available: eclipse-ee4j/parsson 1.1.9 (contains commit 134e8d101aa7)

https://github.com/eclipse-ee4j/parsson/commit/134e8d101aa74c8b9302d0cb62f6ccb4912a9d0c

Vendor Advisories for CVE-2026-9563(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:23 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-17 01:45 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 13:11 UTCGHSA enrichment
  14. 2026-07-16 00:38 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 12:05 UTCGHSA enrichment
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 23:30 UTCGHSA enrichment
  19. 2026-07-14 10:49 UTCGHSA enrichment
  20. 2026-07-13 22:31 UTCEPSS rescore
  21. 2026-07-13 22:16 UTCGHSA enrichment
  22. 2026-07-13 09:42 UTCGHSA enrichment
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-12 21:08 UTCGHSA enrichment
  25. 2026-07-12 08:34 UTCGHSA enrichment
Show 29 more
  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 19:59 UTCGHSA enrichment
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 07:26 UTCGHSA enrichment
  5. 2026-07-10 18:53 UTCGHSA enrichment
  6. 2026-07-10 06:19 UTCGHSA enrichment
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 17:46 UTCGHSA enrichment
  9. 2026-07-09 05:11 UTCGHSA enrichment
  10. 2026-07-08 16:38 UTCGHSA enrichment
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 04:05 UTCGHSA enrichment
  13. 2026-07-07 15:32 UTCGHSA enrichment
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-07 02:35 UTCGHSA enrichment
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 14:01 UTCGHSA enrichment
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-06 01:25 UTCGHSA enrichment
  20. 2026-07-05 12:52 UTCGHSA enrichment
  21. 2026-07-05 02:31 UTCEPSS rescore
  22. 2026-07-05 00:18 UTCGHSA enrichment
  23. 2026-07-04 11:44 UTCGHSA enrichment
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-03 23:08 UTCGHSA enrichment
  26. 2026-07-03 10:33 UTCGHSA enrichment
  27. 2026-07-02 21:56 UTCGHSA enrichment
  28. 2026-07-02 09:23 UTCEG score recompute
  29. 2026-07-02 09:23 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9563?
CVE-2026-9563 is a high vulnerability published on July 2, 2026. 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…
When was CVE-2026-9563 disclosed?
CVE-2026-9563 was first published in the National Vulnerability Database on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9563 actively exploited?
CVE-2026-9563 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9563?
CVE-2026-9563 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-9563?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9563, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9563

Explore →

Is Your Infrastructure Affected by CVE-2026-9563?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs