CVE-2026-60007

HIGHNVD 7.47.4—
EchelonGraph scoreHIGH confidence

Score 7.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-04. NVD baseline CVSS 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.4
EG Score
7.4(high)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
Patch available. Sources: github_commit.
generic

[Eclipse Milo] CVE Reservation Request: Basic128Rsa15 username-token padding oracle (#183) · Issues · Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignment/-/work_items/183
generic

[Eclipse Milo] 6 security findings in Eclipse Milo (#598) · Issues · Eclipse Projects Security / vulnerability-reports · GitLab

https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/598
github_commit Patch Available

commit db59fae993a3 (eclipse-milo/milo)

Patch available: eclipse-milo/milo v1.1.5 (contains commit db59fae993a3)

https://github.com/eclipse-milo/milo/commit/db59fae993a3a1bc66fffc8a2796d444b40285fb

Vendor Advisories for CVE-2026-60007(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 76× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 23:27 UTCEG score recompute
  2. 2026-08-20 23:27 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 11:45 UTCGHSA enrichment
  5. 2026-08-20 00:02 UTCEG score recompute
  6. 2026-08-20 00:01 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 12:17 UTCGHSA enrichment
  9. 2026-08-19 00:36 UTCEG score recompute
  10. 2026-08-19 00:35 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 12:49 UTCGHSA enrichment
  13. 2026-08-18 00:59 UTCEG score recompute
  14. 2026-08-18 00:59 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 13:11 UTCGHSA enrichment
  17. 2026-08-17 01:30 UTCEG score recompute
  18. 2026-08-17 01:30 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 13:48 UTCEG score recompute
  21. 2026-08-16 13:48 UTCGHSA enrichment
  22. 2026-08-16 02:07 UTCGHSA enrichment
  23. 2026-08-15 14:25 UTCGHSA enrichment
  24. 2026-08-15 02:43 UTCEG score recompute
  25. 2026-08-15 02:43 UTCGHSA enrichment
Show 51 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 14:59 UTCGHSA enrichment
  3. 2026-08-14 03:18 UTCEG score recompute
  4. 2026-08-14 03:18 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 15:36 UTCGHSA enrichment
  7. 2026-08-13 03:55 UTCGHSA enrichment
  8. 2026-08-12 16:13 UTCEG score recompute
  9. 2026-08-12 16:13 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 04:32 UTCGHSA enrichment
  12. 2026-08-11 16:50 UTCEG score recompute
  13. 2026-08-11 16:50 UTCGHSA enrichment
  14. 2026-08-11 05:08 UTCEG score recompute
  15. 2026-08-11 05:08 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 17:27 UTCGHSA enrichment
  18. 2026-08-10 05:45 UTCGHSA enrichment
  19. 2026-08-09 18:04 UTCEG score recompute
  20. 2026-08-09 18:04 UTCGHSA enrichment
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-09 06:23 UTCGHSA enrichment
  23. 2026-08-08 18:42 UTCEG score recompute
  24. 2026-08-08 18:42 UTCGHSA enrichment
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-08 07:00 UTCGHSA enrichment
  27. 2026-08-07 19:19 UTCEG score recompute
  28. 2026-08-07 19:19 UTCGHSA enrichment
  29. 2026-08-07 07:37 UTCGHSA enrichment
  30. 2026-08-06 19:56 UTCEG score recompute
  31. 2026-08-06 19:56 UTCGHSA enrichment
  32. 2026-08-06 13:47 UTCEPSS rescore
  33. 2026-08-06 08:14 UTCEG score recompute
  34. 2026-08-06 08:14 UTCGHSA enrichment
  35. 2026-08-05 20:33 UTCEG score recompute▼ 1.70
  36. 2026-08-05 20:33 UTCGHSA enrichment
  37. 2026-08-05 20:32 UTCNVD updateCVSS v3 → 7.4 · severity → HIGH
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-05 18:23 UTCGHSA enrichment
  40. 2026-08-05 14:08 UTCGHSA enrichment
  41. 2026-08-05 09:46 UTCGHSA enrichment
  42. 2026-08-05 05:29 UTCGHSA enrichment
  43. 2026-08-05 01:07 UTCGHSA enrichment
  44. 2026-08-04 20:49 UTCGHSA enrichment
  45. 2026-08-04 16:33 UTCEG score recompute
  46. 2026-08-04 16:33 UTCGHSA enrichment
  47. 2026-08-04 15:38 UTCEG score recompute
  48. 2026-08-04 15:37 UTCGHSA enrichment
  49. 2026-08-04 13:26 UTCEG score recompute
  50. 2026-08-04 12:33 UTCEG score recompute
  51. 2026-08-04 12:33 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-60007?
CVE-2026-60007 is a high vulnerability published on August 4, 2026. 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…
When was CVE-2026-60007 disclosed?
CVE-2026-60007 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-60007 actively exploited?
CVE-2026-60007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.3% of all scored CVEs.
What is the CVSS score of CVE-2026-60007?
CVE-2026-60007 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-60007?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-60007, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-60007

Explore →

Is Your Infrastructure Affected by CVE-2026-60007?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs