View CSAF
Summary
Successful exploitation of these vulnerabilities could allow an attacker to delete protected data, recover user credentials and impersonate legitimate users, or cause the server to stop responding to all clients.
The following versions of Eclipse Foundation Eclipse Milo are affected:
- Eclipse Milo >=0.6.0|<=1.1.4 (CVE-2026-63252, CVE-2026-63248, CVE-2026-60007)
- Eclipse Milo >=1.0.0|<=1.1.4 (CVE-2026-62927, CVE-2026-58080, CVE-2026-61387)
| CVSS |
Vendor |
Equipment |
| v3 8.2 |
Eclipse Foundation |
Eclipse Milo |
| 5 Vulnerabilities |
| Incorrect Authorization, Missing Release of Memory after Effective Lifetime, Missing Authorization, Observable Response Discrepancy, Missing Release of Resource after Effective Lifetime |
Background
- Critical Infrastructure Sectors: Chemical, Critical Manufacturing, Energy, Water and Wastewater
- Countries/Areas Deployed: Worldwide
- Company Headquarters Location: Belgium
Vulnerabilities
CVE-2026-62927
In Eclipse Milo versions 1.0.0 through 1.1.4, the Call service dispatches the original mixed batch to address-space handlers after calculating authorization, allowing an anonymous or otherwise low-privileged client to execute a denied method by batching it with an allowed method.
1 Affected Product
Eclipse Foundation Eclipse Milo: >=1.0.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Additional Metrics
Relevant CWE: CWE-863 Incorrect Authorization
View CVE Details
CVE-2026-63252
In Eclipse Milo versions 0.6.0 through 1.1.4, UASC server transport handlers fail to release retained partial message chunks when a channel disconnects, allowing a remote unauthenticated client to exhaust pooled direct memory by repeatedly sending incomplete chunks and disconnecting, potentially terminating the server.
2 Affected Products
Eclipse Foundation Eclipse Milo: >=1.0.0|<=1.1.4
Product Status: known_affected
Remediations
Eclipse Foundation Eclipse Milo: >=0.6.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Additional Metrics
Relevant CWE: CWE-401 Missing Release of Memory after Effective Lifetime
View CVE Details
CVE-2026-58080
In Eclipse Milo versions 1.0.0 through 1.1.4, OpcUaServerConfig.copy() fails to preserve a configured RoleMapper. On servers that rely on role permissions and construct the running configuration through copy(), sessions receive no role IDs and the default access controller skips role-permission checks, allowing an anonymous client where anonymous sessions are permitted to read role-permission metadata, invoke protected methods, or delete protected nodes.
3 Affected Products
Eclipse Foundation Eclipse Milo: >=1.0.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Eclipse Foundation Eclipse Milo: >=0.6.0|<=1.1.4
Product Status: known_affected
Remediations
Eclipse Foundation Eclipse Milo: >=1.0.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Additional Metrics
Relevant CWE: CWE-862 Missing Authorization
View CVE Details
CVE-2026-63248
In Eclipse Milo versions 0.6.0 through 1.1.4, OPC UA server diagnostics nodes do not enforce access authorization. An anonymous client can enable diagnostics over a None/None endpoint without a certificate; with a trusted client application certificate over SignAndEncrypt, it can read security diagnostics for other active sessions, exposing usernames, login history, authentication mechanisms, security modes and policies, and public client certificates.
4 Affected Products
Eclipse Foundation Eclipse Milo: >=1.0.0|<=1.1.4
Product Status: known_affected
Remediations
Eclipse Foundation Eclipse Milo: >=0.6.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Eclipse Foundation Eclipse Milo: >=1.0.0|<=1.1.4
Product Status: known_affected
Remediations
Eclipse Foundation Eclipse Milo: >=0.6.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Additional Metrics
Relevant CWE: CWE-862 Missing Authorization
View CVE Details
CVE-2026-60007
In Eclipse Milo versions 0.6.0 through 1.1.4, username-token processing returns distinguishable errors for invalid RSA PKCS#1 v1.5 padding and other authentication failures, allowing an on-path attacker who captures a victim’s Basic128Rsa15-encrypted username token to use repeated unauthenticated ActivateSession requests as a padding oracle, recover the victim’s password, and authenticate with the recovered credentials.
5 Affected Products
Eclipse Foundation Eclipse Milo: >=1.0.0|<=1.1.4
Product Status: known_affected
Remediations
Eclipse Foundation Eclipse Milo: >=0.6.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Eclipse Foundation Eclipse Milo: >=1.0.0|<=1.1.4
Product Status: known_affected
Remediations
Eclipse Foundation Eclipse Milo: >=0.6.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Eclipse Foundation Eclipse Milo: >=0.6.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Additional Metrics
Relevant CWE: CWE-204 Observable Response Discrepancy
View CVE Details
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.
6 Affected Products
Eclipse Foundation Eclipse Milo: >=1.0.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Eclipse Foundation Eclipse Milo: >=0.6.0|<=1.1.4
Product Status: known_affected
Remediations
Eclipse Foundation Eclipse Milo: >=1.0.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Eclipse Foundation Eclipse Milo: >=0.6.0|<=1.1.4
Product Status: known_affected
Remediations
Eclipse Foundation Eclipse Milo: >=0.6.0|<=1.1.4
Product Status: known_affected
Remediations
Eclipse Foundation Eclipse Milo: >=1.0.0|<=1.1.4
Product Status: known_affected
Remediations
Vendor fix
The Eclipse Foundation recommends users upgrade to Eclipse Milo 1.1.5 https://github.com/eclipse-milo/milo/releases/tag/v1.1.5.
Mitigation
For users on Milo 0.6.x, there are no 0.6.x releases with the fixes, which requires users to migrate to Milo 1.1.5 or later.
Additional Metrics
Relevant CWE: CWE-772 Missing Release of Resource after Effective Lifetime
View CVE Details
Acknowledgments
- Abhinav Agarwal reported these vulnerabilities to CISA.
Legal Notice and Terms of Use
This product is provided subject to this Notification (https://www.cisa.gov/notification) and this Privacy & Use policy (https://www.cisa.gov/privacy-policy).
Recommended Practices
CISA recommends users take defensive measures to minimize the risk of exploitation of these vulnerabilities.
- Minimize network exposure for all control system devices and/or systems, ensuring they are not accessible from the internet.
- Locate control system networks and remote devices behind firewalls and isolating them from business networks.
- When remote access is required, use more secure methods, such as Virtual Private Networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize VPN is only as secure as the connected devices.
CISA reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures.
CISA also provides a section for control systems security recommended practices on the ICS webpage on cisa.gov/ics. Several CISA products detailing cyber defense best practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies.
CISA encourages organizations to implement recommended cybersecurity strategies for proactive defense of ICS assets.
Additional mitigation guidance and recommended practices are publicly available on the ICS webpage at cisa.gov/ics in the technical information paper, ICS-TIP-12-146-01B–Targeted Cyber Intrusion Detection and Mitigation Strategies.
Organizations observing suspected malicious activity should follow established internal procedures and report findings to CISA for tracking and correlation against other incidents.
Revision History
- Initial Release Date: 2026-10-15
| Date |
Revision |
Summary |
| 2026-10-15 |
1 |
Initial Publication |
Legal Notice and Terms of Use