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

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

Related CVEs(same vendor + same CWE)

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 70.3% 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