Skip to main content
VulnerabilityPublished

CVE-2026-1188: Eclipse OMR · Incorrect Calculation of Buffer Size

Affects Eclipse OMRSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium : upgrade to 0.8.0 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.8.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Eclipse OMR to 0.8.0.

Affected software

ProductAffectedFixed in
Eclipse FoundationEclipse OMRAffected
  • >=0.2.0 <0.8.0
Fixed in
  • 0.8.0
GitHubeclipse-omr/omrpkg:github/eclipse-omr/omrOther threatsAffected
  • =0.2.0
Fixed in–
GitHubEclipse OMRpkg:github/Eclipse OMROther threatsAffected
  • >=0.2.0 <0.8.0
Fixed in
  • 0.8.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately assess their use of Eclipse OMR and identify any deployments of versions 0.2.0 through prior to 0.8.0. The primary mitigation is to upgrade to Eclipse OMR version 0.8.0 or later, where the buffer size calculation issue has been fixed. If upgrading is not immediately feasible, organizations should audit and restrict access to services or applications using the vulnerable library to trusted networks only, minimizing exposure to remote attackers. Developers should review any custom code interfacing with the affected API to ensure buffer sizes are correctly calculated, including separators, to prevent overflow. Employing runtime protections such as Address Space Layout Randomization (ASLR), Data Execution Prevention (DEP), and stack canaries can help mitigate exploitation impact. Monitoring logs for abnormal crashes or memory errors related to Eclipse OMR components can provide early detection of exploitation attempts. Finally, organizations should maintain an inventory of open-source components and apply timely patches to reduce exposure to such vulnerabilities.

Description

CVE-2026-1188 is a medium severity buffer overflow vulnerability in the Eclipse OMR port library component versions starting from 0.2.0. The flaw arises because an API function that returns textual names of supported processor features miscalculates the required buffer size by not accounting for separators between features. This can lead to a buffer overflow if the output buffer is undersized, potentially causing memory corruption. The vulnerability requires no authentication or user interaction and can be exploited remotely. It is fixed in Eclipse OMR version 0.8.0. Although no known exploits are currently reported in the wild, the vulnerability poses a risk to systems using affected versions of Eclipse OMR, particularly in environments where this library is integrated.

References

Community reviews

Loading reviews…