CVE-2026-9563

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this weekElevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 2, 2026

Last Modified

July 2, 2026

Advisory Details (5)

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

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

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

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

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

GitHub - eclipse-ee4j/parsson at 1.1.8 · GitHub

https://github.com/eclipse-ee4j/parsson/tree/1.1.8
GitHub pull request 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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-trustyai-service-rhel9:17917925252026-10-19redhat
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 11× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 263 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 164 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-9563?
CVE-2026-9563 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-9563 published?
The CVE record for CVE-2026-9563 was published on July 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 2, 2026; the record at its source may have been updated since.
Is CVE-2026-9563 actively exploited?
CVE-2026-9563 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9563?
CVE-2026-9563 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-9563?
A fix for CVE-2026-9563 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-9563 are linked in the Vendor Advisories panel on this page.

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.