Resource exhaustion in Eclipse Milo
CVE-2026-61387
In Eclipse Milo versions 1.0.0 through 1.1.4, monitored-item quota accounting is not exception-safe: if item creation fails with an unchecked error, the server-global reservation is not restored. Deeply nested PubSub ExtensionObjects in a `CreateMonitoredItems` event filter can trigger a `StackOverflowError` during decoding, allowing an unauthenticated remote client to exhaust a finite global monitored-item quota and prevent all clients from creating new monitored items until restart. Existing monitored items and other server functions remain unaffected.
Vulnerability class: DoS (Denial of Service)
EPSS: 0.003 (27.9th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
Affected products
- Eclipse Milo
- Eclipse Foundation Milo — versions 1.0.0
Weakness classification (CWE)
References
- emo@eclipse.org (Patch)
- emo@eclipse.org (Patch)
- emo@eclipse.org (Issue Tracking, Vendor Advisory)
- emo@eclipse.org (Broken Link)
Frequently asked questions
- What is CVE-2026-61387?
- CVE-2026-61387 is a high-severity vulnerability in Eclipse Milo, classified under Uncontrolled Resource Consumption. CVSS score: 7.5/10. Published 2026-08-04.
- How severe is CVE-2026-61387?
- High severity. CVSS v3 base score is 7.5 out of 10.