CVE-2026-60007

Padding Oracle in Eclipse Milo Reveals Passwords

Published Aug 4, 2026 CVSS 4.0 · 9.1 Critical EPSS < 1% KEV · Not listed

Description

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.

Analysis

Technical impact

Eclipse Milo versions 0.6.0 through 1.1.4 process username tokens by returning distinguishable errors for invalid RSA PKCS#1 v1.5 padding and other authentication failures. An on-path attacker who captures a victim's Basic128Rsa15 encrypted username token can send repeated unauthenticated ActivateSession requests, relying on the differing error responses to perform a padding oracle attack. This allows the attacker to recover the victim's password and authenticate using the recovered credentials. The flaw is a classic padding oracle weakness (CWE-204) with full confidentiality and authentication compromise.

Affected Systems

The vulnerable product is Eclipse Milo under the Eclipse Foundation. The affected range is versions 0.6.0 through 1.1.4 inclusive. No explicit sub-product variants are listed in the data.

Risk and Exploitability

The CVSS base score is 9.1, indicating high severity. EPSS data is not available and the vulnerability is not listed in CISA KEV. The attack requires an on-path position to intercept a Basic128Rsa15 token and the ability to send many ActivateSession requests; it does not require privileged user interaction, making exploitation feasible for network attackers against exposed Milo services.

Affected Products

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

Eclipse Foundation

Eclipse Milo

unaffected

Version	Status	Constraints
`0.6.0`	affected	≤ 1.1.4

Configuration 1 [-]

cpe:2.3:a:eclipse:milo:*:*:*:*:*:*:*:*

No data.

Vendor Product Versions

Eclipse

Eclipse Milo

Version	Status	Scheme	Platform
`[0.6.0,1.1.4]`	affected	semver	—

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

Disable the Basic128Rsa15 username token authentication or restrict its use to trusted internal networks.
Monitor for repeated failed ActivateSession attempts and enforce network segmentation or firewall rules to limit access to the Milo endpoint.
Apply any vendor‑released patch or upgrade to a newer version of Eclipse Milo that includes the secure padding verification fix.

Generated by OpenCVE AI on August 4, 2026 at 20:31 UTC.

Tracking

Advisories

No advisories available

Metrics

Attack Vector Network

Attack Complexity Low

Privileges Required None

Attack Requirements Present

User Interaction None

Vulnerable System Confidentiality Impact High

Vulnerable System Integrity Impact High

Vulnerable System Availability Impact None

Subsequent System Confidentiality Impact None

Subsequent System Integrity Impact None

Subsequent System Availability Impact None

Attack Vector Network

Attack Complexity High

Privileges Required None

Scope Unchanged

Confidentiality Impact High

Integrity Impact High

Availability Impact None

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Exploit prediction score: < 1% (0.553% probability within 30 days)

Exploitation none

Automatable no

Technical Impact partial

References

Link	Providers
https://github.com/eclipse-milo/milo/commit/db59fae993a3a1bc66fffc8a2796d444b40285fb
https://gitlab.eclipse.org/security/cve-assignment/-/work_items/183
https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/598

History

Aug 5, 2026 10:45 AM First appearance in the feed. Affected vendors updated View changes

Type	Values Removed	Values Added
First Time appeared		Eclipse Eclipse eclipse Milo
Vendors & Products		Eclipse Eclipse eclipse Milo

Aug 4, 2026 9:00 PM Title updated View changes

Type	Values Removed	Values Added
Title		Padding Oracle in Eclipse Milo Reveals Passwords

Aug 4, 2026 3:30 PM Scoring metrics updated View changes

Type	Values Removed	Values Added
Metrics		ssvc `{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}`

Aug 4, 2026 12:45 PM Description updated. Weaknesses updated. Added references. Scoring metrics updated View changes

Type	Values Removed	Values Added
Description		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.
Weaknesses		CWE-204
References		https://github.com/eclipse-milo/milo/commit/db59fae993a3a1bc66fffc8a2796d444b40285fb https://gitlab.eclipse.org/security/cve-assignment/-/work_items/183 https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/598
Metrics		cvssV4_0 `{'score': 9.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}`