CVE-2026-60104

HIGHNVD 8.08.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.0 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekElevated
8.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.0Exploit: Elevated riskExposed: 0

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

Bitwarden Server before 2026.6.0 does not verify that the email in a POST /auth-requests/admin-request body belongs to the authenticated caller, allowing a low-privileged organization member to obtain another user's vault key and a victim-scoped access token by creating a Trusted Device Encryption authentication request, bound to an attacker-controlled public key, that is readable from an unauthenticated endpoint once approved resulting in disclosure of the victim's vault key and account takeover.

CVSS v3
8.0
EG Score
8.0(medium)
EG Risk
52(Track*)
EG Risk 52/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
Severity80% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 20, 2026

Advisory Details (5)

Auto-updated Jul 8, 2026
Patch available. Sources: github_commit, github_pr.
generic

Bitwarden Server < 2026.6.0 Authorization Bypass via Admin Auth Request | Advisories | VulnCheck

https://www.vulncheck.com/advisories/bitwarden-server-authorization-bypass-via-admin-auth-request
generic

Sanjok Karki | Offensive Security Engineer

https://sanjokkarki.com.np/blog/bitwarden-vault-key-heist
generic

Releases · bitwarden/server · GitHub

https://github.com/bitwarden/server/releases#release-v2026.6.0
github_pr Patch Available

[PM-35401] Update exception handling in CreateAuthRequestAsync() and PostAdminRequest()

Patch available: bitwarden/server v2026.6.0 (PR #7615 merged 2026-05-21)

https://github.com/bitwarden/server/pull/7615
github_commit Patch Available

commit dcf4c486b2b5 (bitwarden/server)

Patch available: bitwarden/server v2026.6.0 (contains commit dcf4c486b2b5)

https://github.com/bitwarden/server/commit/dcf4c486b2b5bedecc03a48b427243328cc74a9a

Vendor Advisories for CVE-2026-60104(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 24× in last 7d / 64× 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-07-29 08:05 UTCGHSA enrichment
  2. 2026-07-28 20:37 UTCEG score recompute
  3. 2026-07-28 20:37 UTCGHSA enrichment
  4. 2026-07-28 15:37 UTCEPSS rescore
  5. 2026-07-28 09:21 UTCGHSA enrichment
  6. 2026-07-27 22:04 UTCEG score recompute
  7. 2026-07-27 22:04 UTCGHSA enrichment
  8. 2026-07-27 14:14 UTCEPSS rescore
  9. 2026-07-27 10:49 UTCGHSA enrichment
  10. 2026-07-26 23:37 UTCEG score recompute
  11. 2026-07-26 23:37 UTCGHSA enrichment
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 14:54 UTCEPSS rescore
  14. 2026-07-26 12:26 UTCEG score recompute
  15. 2026-07-26 12:26 UTCGHSA enrichment
  16. 2026-07-25 14:18 UTCEPSS rescore
  17. 2026-07-25 14:18 UTCEPSS rescore
  18. 2026-07-24 14:18 UTCEPSS rescore
  19. 2026-07-24 14:18 UTCEPSS rescore
  20. 2026-07-23 14:18 UTCEPSS rescore
  21. 2026-07-23 14:18 UTCEPSS rescore
  22. 2026-07-23 03:21 UTCEG score recompute▲ 0.70
  23. 2026-07-22 14:08 UTCEPSS rescore
  24. 2026-07-22 14:08 UTCEPSS rescore
  25. 2026-07-21 15:25 UTCEPSS rescore
Show 39 more
  1. 2026-07-21 15:25 UTCEPSS rescore
  2. 2026-07-20 17:08 UTCEPSS rescore
  3. 2026-07-20 14:36 UTCNVD updateCVSS v3 → 8
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 05:16 UTCGHSA enrichment
  8. 2026-07-16 18:04 UTCGHSA enrichment
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-16 06:53 UTCGHSA enrichment
  11. 2026-07-15 19:42 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 08:30 UTCGHSA enrichment
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 21:18 UTCGHSA enrichment
  17. 2026-07-14 10:07 UTCGHSA enrichment
  18. 2026-07-13 22:56 UTCGHSA enrichment
  19. 2026-07-13 22:31 UTCEPSS rescore
  20. 2026-07-13 11:44 UTCGHSA enrichment
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-13 00:32 UTCGHSA enrichment
  24. 2026-07-12 13:20 UTCGHSA enrichment
  25. 2026-07-12 05:46 UTCEPSS rescore
  26. 2026-07-12 02:09 UTCGHSA enrichment
  27. 2026-07-11 14:58 UTCGHSA enrichment
  28. 2026-07-11 08:27 UTCEPSS rescore
  29. 2026-07-11 08:27 UTCEPSS rescore
  30. 2026-07-11 03:47 UTCGHSA enrichment
  31. 2026-07-10 16:35 UTCGHSA enrichment
  32. 2026-07-10 05:23 UTCGHSA enrichment
  33. 2026-07-09 19:10 UTCEPSS rescore
  34. 2026-07-09 19:10 UTCEPSS rescore
  35. 2026-07-09 18:11 UTCGHSA enrichment
  36. 2026-07-09 06:57 UTCGHSA enrichment
  37. 2026-07-08 21:39 UTCMITRE cvelistV5CVSS v3 → 8.7 · CVSS v4 → 9.3
  38. 2026-07-08 19:46 UTCEG score recompute
  39. 2026-07-08 19:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-60104?
CVE-2026-60104 is a high vulnerability published on July 8, 2026. Bitwarden Server before 2026.6.0 does not verify that the email in a POST /auth-requests/admin-request body belongs to the authenticated caller, allowing a low-privileged organization member to obtain another user's vault key and a victim-scoped access token by creating a Trusted Device Encryption…
When was CVE-2026-60104 disclosed?
CVE-2026-60104 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-60104 actively exploited?
CVE-2026-60104 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 86.7% of all scored CVEs.
What is the CVSS score of CVE-2026-60104?
CVE-2026-60104 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2026-60104?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-60104, 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-60104

Explore →

Is Your Infrastructure Affected by CVE-2026-60104?

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

Start Free Scan →Browse All CVEs