CVE-2026-1188CWE-131

In the Eclipse OMR port library component since release 0.2.0, an API function to return the textual names of all supported processor features was not…

Medium · published January 29, 2026

CVSS v4.0
6.9
EPSS
0%
Percentile
41.5
In the wild
Unconfirmed
What it is

⚠️ A sneaky buffer overflow could trip you up if your output sizing misses a critical separator! When using the Eclipse OMR port library, this simple oversight can turn into a headache for developers. 💥 Think of it like a crowded restaurant where the staff forget the spacing between tables. If they try to fit too many customers into a small area without accounting for the space needed for each table's seating, chaos ensues! Similarly, if the output buffer doesn't consider the separator, your data can overflow like a table piled too high with dishes. An attacker may exploit this vulnerability to potentially overwrite adjacent memory, leading to unexpected behavior or crashes in applications using the Eclipse OMR library. While it's not currently known to be exploited, it could pave the way for future vulnerabilities if left unattended.

Put simply

Think of it like a crowded restaurant where the staff forget the spacing between tables. If they try to fit too many customers into a small area without accounting for the space needed for each table's seating, chaos ensues! Similarly, if the output buffer doesn't consider the separator, your data can overflow like a table piled too high with dishes. This vulnerability arises from an API function within the Eclipse OMR library that fails to accurately account for the separator between processor features when determining the size of the output buffer. This oversight can trigger a buffer overflow, causing unpredictable effects.

What to do

An attacker may exploit this vulnerability to potentially overwrite adjacent memory, leading to unexpected behavior or crashes in applications using the Eclipse OMR library. While it's not currently known to be exploited, it could pave the way for future vulnerabilities if left unattended. To protect your application, promptly update to Eclipse OMR version 0.8.0, which addresses this issue. Additionally, review your buffer management practices to ensure output sizes are appropriately calculated to avoid future vulnerabilities. You've got this! By taking these steps, you're fortifying your application and keeping it secure! 🛡️

The record
Technical detail
CVSS v4.0
6.9 · MEDIUM
Vector
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
EPSS
0.00494 · 41.5th percentile
Weakness
CWE-131 · Incorrect Calculation of Buffer Size
Published
2026-01-29T08:36Z
EPSS history
Timeline
  • 29 JAN 08:36Z
    In the Eclipse OMR port library component since release 0.2.0, an API function to return the textual names of all supported processor features was not…
    cvelistv5