CVE-2026-6918

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

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.5(medium)
EPSS
40.5%
KEV
Not listed

Published

May 5, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated May 5, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

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
generic

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 / EcosystemFixed in / 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 10× in last 7d / 43× 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 122 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-6918?
CVE-2026-6918 is a high vulnerability 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 disclosed?
CVE-2026-6918 was first published in the National Vulnerability Database on May 5, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6918 actively exploited?
CVE-2026-6918 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6918, 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-6918

Explore →

Is Your Infrastructure Affected by CVE-2026-6918?

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

Start Free Scan →Browse All CVEs