LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1188: In the Eclipse OMR port library component since release 0.2.0, an API function to return the textual names...

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 accounting for the separator inserted between processor features. If the output buffer supplied to this function was incorrectly sized, failing to account for the separator when determining when a write to the buffer was safe could lead to a buffer overflow. This issue is fixed in Eclipse OMR version 0.8.0.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1188 is a buffer overflow flaw in Eclipse OMR’s port library. A function that lists processor feature names can write past a caller-provided buffer if the buffer size calculation omits separators. Eclipse states the issue is fixed in OMR 0.8.0. Business risk depends on whether OMR is embedded in exposed software paths.

Executive priority

Treat as a moderate-priority dependency issue. It has a published fix and no cited active exploitation, but the no-auth network CVSS characteristics justify timely inventory and upgrade planning, especially for exposed services or widely distributed products embedding Eclipse OMR.

Technical view

The flaw is CWE-131: incorrect buffer size calculation. The affected API did not account for separators inserted between processor feature names when deciding whether a write was safe. The CVE record assigns CVSS 4.0 score 6.9, vector AV:N/AC:L/PR:N/UI:N with low confidentiality, integrity, and availability impacts.

Likely exposure

Exposure is most likely in products or services that embed Eclipse OMR versions after 0.2.0 and before the fixed 0.8.0 release. The provided affected data is limited, so teams should confirm exact version ranges and bundled copies from Eclipse OMR guidance and their own dependency inventory.

Exploitation context

No provided source reports active exploitation, and the CVE is not marked in CISA KEV. The CVSS vector indicates network attackability without privileges or user interaction, but practical exploitability depends on whether an application exposes code paths using the vulnerable API with incorrectly sized buffers.

Researcher notes

The public detail identifies the bug class and fix but not a weaponized exploit. The key research questions are exact affected version boundaries, downstream projects embedding OMR, and whether reachable application paths pass undersized buffers to the feature-name API.

Mitigation direction

  • Upgrade Eclipse OMR to version 0.8.0 or later where feasible.
  • Check vendor guidance for products that bundle or statically link Eclipse OMR.
  • Rebuild dependent applications after updating embedded OMR source or libraries.
  • Prioritize internet-facing services if they include vulnerable OMR code paths.

Validation and detection

  • Inventory Eclipse OMR versions in source, dependencies, containers, and vendor components.
  • Confirm whether bundled OMR is older than fixed version 0.8.0.
  • Review whether applications call the processor feature-name API.
  • Track remediation evidence through build manifests or software composition analysis results.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-131: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1188 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-1188Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Eclipse FoundationEclipse OMR0.2.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-131 · source CWE mapping

Incorrect Calculation of Buffer Size

Incorrect Calculation of Buffer Size represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.