CVE-2026-60007: In Eclipse Milo versions 0.6.0 through 1.1.4, username-token processing returns distinguishable errors for invalid RSA…
CVE-2026-60007 · Severity: high · CVSS 7.4 · Published 2026-08-04
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.
No. Junglewise Threat Intelligence has no report of CVE-2026-60007 being exploited in the wild.
How severe is CVE-2026-60007?
High severity, with a CVSS score of 7.4, published 4 August 2026.
Which products and versions are affected?
Eclipse Milo. The advisory does not name versions.
Is there a fix for CVE-2026-60007?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-60007?
Check whether you run Eclipse Milo. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.