CVE-2026-9563

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM 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
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
EG Risk
39(Track)
EG Risk 39/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%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
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(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-trustyai-service-rhel9:17881986812026-09-08redhat
redhatdevspaces/pluginregistry-rhel9:17877597232026-09-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 67× 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.

Showing the most recent 100 of 219 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 06:22 UTCEG score recompute
  3. 2026-09-18 06:22 UTCVendor advisory
  4. 2026-09-18 06:22 UTCGHSA enrichment
  5. 2026-09-17 19:32 UTCEPSS rescore
  6. 2026-09-16 14:09 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-14 00:18 UTCEG score recompute
  10. 2026-09-14 00:18 UTCVendor advisory
  11. 2026-09-14 00:18 UTCGHSA enrichment
  12. 2026-09-13 16:48 UTCEPSS rescore
  13. 2026-09-13 09:03 UTCEG score recompute
  14. 2026-09-13 09:03 UTCVendor advisory
  15. 2026-09-13 09:03 UTCGHSA enrichment
  16. 2026-09-12 15:02 UTCEPSS rescore
  17. 2026-09-12 14:32 UTCEG score recompute
  18. 2026-09-12 14:32 UTCVendor advisory
  19. 2026-09-12 14:32 UTCGHSA enrichment
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 09:38 UTCEPSS rescore
  22. 2026-09-10 09:35 UTCEPSS rescore
  23. 2026-09-08 22:01 UTCEPSS rescore
  24. 2026-09-06 14:23 UTCEG score recompute
  25. 2026-09-06 14:23 UTCVendor advisory
Show 75 more
  1. 2026-09-06 14:23 UTCGHSA enrichment
  2. 2026-09-06 13:48 UTCEPSS rescore
  3. 2026-09-06 00:33 UTCEG score recompute
  4. 2026-09-06 00:33 UTCVendor advisory
  5. 2026-09-06 00:33 UTCGHSA enrichment
  6. 2026-09-05 15:31 UTCEPSS rescore
  7. 2026-09-04 05:07 UTCEPSS rescore
  8. 2026-09-02 14:12 UTCEPSS rescore
  9. 2026-09-01 13:54 UTCEPSS rescore
  10. 2026-09-01 04:40 UTCEPSS rescore
  11. 2026-08-31 00:00 UTCEG score recompute
  12. 2026-08-31 00:00 UTCGHSA enrichment
  13. 2026-08-30 19:18 UTCEPSS rescore
  14. 2026-08-30 11:26 UTCEG score recompute
  15. 2026-08-30 11:26 UTCGHSA enrichment
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:42 UTCEPSS rescore
  18. 2026-08-27 22:20 UTCEG score recompute
  19. 2026-08-27 22:20 UTCGHSA enrichment
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:47 UTCEPSS rescore
  22. 2026-08-25 16:04 UTCEG score recompute
  23. 2026-08-25 16:04 UTCGHSA enrichment
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-24 22:59 UTCEG score recompute
  26. 2026-08-24 22:59 UTCGHSA enrichment
  27. 2026-08-24 14:18 UTCEPSS rescore
  28. 2026-08-24 10:25 UTCEG score recompute
  29. 2026-08-24 10:25 UTCGHSA enrichment
  30. 2026-08-23 20:53 UTCGHSA enrichment
  31. 2026-08-23 08:19 UTCEG score recompute
  32. 2026-08-23 08:19 UTCGHSA enrichment
  33. 2026-08-23 00:19 UTCEPSS rescore
  34. 2026-08-22 19:44 UTCGHSA enrichment
  35. 2026-08-22 06:44 UTCEG score recompute
  36. 2026-08-22 06:44 UTCGHSA enrichment
  37. 2026-08-21 23:49 UTCEPSS rescore
  38. 2026-08-21 18:07 UTCGHSA enrichment
  39. 2026-08-21 05:30 UTCEG score recompute
  40. 2026-08-21 05:30 UTCGHSA enrichment
  41. 2026-08-20 22:56 UTCEPSS rescore
  42. 2026-08-20 16:57 UTCGHSA enrichment
  43. 2026-08-20 04:24 UTCEG score recompute
  44. 2026-08-20 04:24 UTCGHSA enrichment
  45. 2026-08-19 17:04 UTCEPSS rescore
  46. 2026-08-19 13:31 UTCGHSA enrichment
  47. 2026-08-19 00:58 UTCEG score recompute
  48. 2026-08-19 00:58 UTCGHSA enrichment
  49. 2026-08-18 13:49 UTCEPSS rescore
  50. 2026-08-18 11:52 UTCGHSA enrichment
  51. 2026-08-17 22:58 UTCEG score recompute
  52. 2026-08-17 22:58 UTCGHSA enrichment
  53. 2026-08-17 13:47 UTCEPSS rescore
  54. 2026-08-17 08:18 UTCGHSA enrichment
  55. 2026-08-16 19:45 UTCEG score recompute
  56. 2026-08-16 19:45 UTCGHSA enrichment
  57. 2026-08-16 14:56 UTCEPSS rescore
  58. 2026-08-16 07:05 UTCEG score recompute
  59. 2026-08-16 07:05 UTCGHSA enrichment
  60. 2026-08-16 02:15 UTCEPSS rescore
  61. 2026-08-15 18:33 UTCGHSA enrichment
  62. 2026-08-15 06:00 UTCEG score recompute
  63. 2026-08-15 06:00 UTCGHSA enrichment
  64. 2026-08-15 01:31 UTCEPSS rescore
  65. 2026-08-14 17:27 UTCGHSA enrichment
  66. 2026-08-14 04:43 UTCEG score recompute
  67. 2026-08-14 04:43 UTCGHSA enrichment
  68. 2026-08-13 22:00 UTCEPSS rescore
  69. 2026-08-13 16:10 UTCGHSA enrichment
  70. 2026-08-13 03:26 UTCGHSA enrichment
  71. 2026-08-12 14:53 UTCEG score recompute
  72. 2026-08-12 14:53 UTCGHSA enrichment
  73. 2026-08-12 13:51 UTCEPSS rescore
  74. 2026-08-12 02:20 UTCGHSA enrichment
  75. 2026-08-11 13:47 UTCEG score recompute

Related CVEs(same vendor + 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 1% probability of exploitation in the next 30 days, which ranks it in the top 51.3% of all scored CVEs.
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