# CVE-2026-60007: Information disclosure in Eclipse Milo

> An on-path attacker can recover victim passwords via a padding oracle in Eclipse Milo, enabling unauthorized authentication and data access.

- **Severity:** Critical 9.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-jrjq-9cmf-3h6f

## What is CVE-2026-60007?

CVE-2026-60007 is a critical vulnerability in Eclipse Milo, published on 4 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-204 (Observable Response Discrepancy)

## Which versions are affected by CVE-2026-60007?

It affects 1 product.


Products: Eclipse Milo.

## How do I fix CVE-2026-60007?

No fix has been published for CVE-2026-60007 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-60007 being exploited?

There is no known exploitation of CVE-2026-60007 in the wild and no public exploit code.

## Other vulnerabilities in Eclipse Milo

- [CVE-2026-58080](https://insights.sbomify.com/CVE-2026-58080/): Missing authorization in Eclipse Milo (high 8.8)
- [CVE-2026-62927](https://insights.sbomify.com/CVE-2026-62927/): Missing authorization in Eclipse Milo (high 8.7)
- [CVE-2026-63252](https://insights.sbomify.com/CVE-2026-63252/): Denial of service in Eclipse Milo (high 8.7)
- [CVE-2026-61387](https://insights.sbomify.com/CVE-2026-61387/): Denial of service in Eclipse Milo (medium 6.9)
- [CVE-2026-63248](https://insights.sbomify.com/CVE-2026-63248/): Missing authorization in Eclipse Milo (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-60007 and fix it if it is affected.

What it is: CVE-2026-60007 is a critical vulnerability in Eclipse Milo, published on 4 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-60007 in the wild and no public exploit code.

Affected product: Eclipse Milo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-60007/ (Markdown: https://insights.sbomify.com/CVE-2026-60007/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-60007
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-60007
- OSV: https://osv.dev/vulnerability/CVE-2026-60007

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-60007/
Summaries are generated and may contain mistakes; the official description above is the record.