CVE-2026-6918

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.2% (67th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated 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: 1.2%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

In Eclipse Open9J versions 0.21 to 0.58, a pre-authentication remote attacker can crash JITServer by sending a 32-byte crafted TCP message.

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 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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
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
1.2%
EPSS %ILE
67th
KEV
Not listed

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

May 5, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated May 5, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Pre-auth remote OOB heap read in JITServer Message::deserialize() via crafted DataDescriptor._size · Advisory · eclipse-openj9/openj9 · GitHub

https://github.com/eclipse-openj9/openj9/security/advisories/GHSA-q393-vr4c-969r
Web page

Prevent JITServer buffer overrun by mpirvu · Pull Request #23793 · eclipse-openj9/openj9 · GitHub

https://github.com/eclipse-openj9/openj9/pull/23793

Vendor Advisories for CVE-2026-6918(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjava-21-ibm-semeru-certified-jdk-1:21.0.11.0.10-2.el10_12026-06-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 13× in last 7d / 32× 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 97 of 223 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 126 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-6918?
CVE-2026-6918 is a high-severity vulnerability; its CVE record was published on May 5, 2026. In Eclipse Open9J versions 0.21 to 0.58, a pre-authentication remote attacker can crash JITServer by sending a 32-byte crafted TCP message.
When was CVE-2026-6918 made public?
CVE-2026-6918 was made public on May 5, 2026: that is the date its CVE record's CNA, Eclipse Foundation, gives for when the vulnerability was made public. The CVE record itself was published on May 5, 2026. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-6918 actively exploited?
CVE-2026-6918 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6918?
CVE-2026-6918 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-6918?
A fix for CVE-2026-6918 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-6918 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-6918?

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

Book a Demo →Browse All CVEs