CVE-2026-16243

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory published 2026-07-21. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

In Eclipse OMR versions up to 0.11, the arraycmp SIMD implementation for Z and P does not check if the number of bytes to compare is zero.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

July 21, 2026

Last Modified

August 11, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic

Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignment/-/work_items/195
github_pr

Fix handling of zero length arraycmp/arraycmplen on Power

Fix merged in eclipse-omr/omr PR #8349 on 2026-07-20 — awaiting tagged release

https://github.com/eclipse-omr/omr/pull/8349
github_pr

Fix the arraycmp SIMD evaluator on IBM Z

Fix merged in eclipse-omr/omr PR #8348 on 2026-07-20 — awaiting tagged release

https://github.com/eclipse-omr/omr/pull/8348

Vendor Advisories for CVE-2026-16243(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
redhatjava-21-ibm-semeru-certified-jdk-1:21.0.12.0.8-1.el10_02026-08-10redhat
redhatjava-1.8.0-ibm-1:1.8.0.8.70-1.el8_102026-08-10redhat

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(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 116× 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 233 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-16243?
CVE-2026-16243 is a high vulnerability published on July 21, 2026. In Eclipse OMR versions up to 0.11, the arraycmp SIMD implementation for Z and P does not check if the number of bytes to compare is zero.
When was CVE-2026-16243 disclosed?
CVE-2026-16243 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16243 actively exploited?
CVE-2026-16243 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.8% of all scored CVEs.
What is the CVSS score of CVE-2026-16243?
CVE-2026-16243 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-16243?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16243, 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-16243

Explore →

Is Your Infrastructure Affected by CVE-2026-16243?

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

Start Free Scan →Browse All CVEs