CVE-2026-16243: In Eclipse OMR versions up to 0.11, the arraycmp SIMD implementation for Z and P does not check if the number

Routine

HIGH 7.5REMOTEUPGRADE

CVE-2026-16243 is a high-severity flaw (CVSS 7.5) affecting omr. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 71%)
CISA exploited list	No
Weakness	CWE-125
Published	2026-07-21
Last modified	2026-10-24

Publisher (CNA): Eclipse Foundation · Vendor: eclipse

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-21 18:16 UTCPublished CVE record published
2026-10-24 19:10 UTCUpdated Record last modified

eclipse omr UPGRADE

Affected: >= 0.1.0 and <= 0.10.0

Fixed in: newer than 0.10.0

Safe to downgrade to: a release before 0.1.0

1. Check installed version

apt-cache policy omr || rpm -q omr || omr --version

2. UPGRADE to newer than 0.10.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade omr

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade omr

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 0.1.0 (Debian / Ubuntu)

apt-cache madison omr sudo apt install omr=<VERSION_BEFORE_0.1.0> sudo apt-mark hold omr

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list omr sudo dnf downgrade omr-<VERSION_BEFORE_0.1.0> sudo dnf versionlock add omr

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-16243?

omr: upgrade to newer than 0.10.0. Exact commands for each OS are on this page.

Is CVE-2026-16243 being exploited?

CVE-2026-16243 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-16243 affect?

CVE-2026-16243 affects omr. Severity is high (CVSS 7.5). 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.

How urgent is CVE-2026-16243?

Priority 39/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs