Memory corruption via processor-feature separator miscalculation
Published Jan 29, 2026 · Updated Jan 29, 2026
Buffer overflow in Eclipse OMR before 0.8.0 allows remote attackers to corrupt memory via a processor-feature string request. The omrsysinfo_get_processor_feature_string function checks feature-name bytes against the caller's output-buffer size but omits the inserted separator from its remaining-space calculation. An unauthenticated network path in a consuming runtime must supply an undersized buffer; the overflow can alter adjacent memory or interrupt the process.
Summary
What happened
Buffer overflow in Eclipse OMR before 0.8.0 allows remote attackers to corrupt memory via a processor-feature string request. The omrsysinfo_get_processor_feature_string function checks feature-name bytes against the caller's output-buffer size but omits the inserted separator from its remaining-space calculation. An unauthenticated network path in a consuming runtime must supply an undersized buffer; the overflow can alter adjacent memory or interrupt the process.
The record
- CVE
- CVE-2026-1188
- Published
- Jan 29, 2026
- Updated
- Jan 29, 2026
- Vendor
- The Eclipse Foundation
- Product
- Eclipse OMR
- Classifications
- CWE-120, CWE-131
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2026CVE publishedPublication date reported by the CVE source.
- Jan 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.2.0 <0.8.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo