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.
CVE-2026-60104
This high-severity CVE scores 7.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(low)
- EPSS
- —
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 8, 2026
Advisory Details (5)
Auto-updated Jul 8, 2026Bitwarden Server < 2026.6.0 Authorization Bypass via Admin Auth Request | Advisories | VulnCheck
https://www.vulncheck.com/advisories/bitwarden-server-authorization-bypass-via-admin-auth-requestSanjok Karki | Offensive Security Engineer
https://sanjokkarki.com.np/blog/bitwarden-vault-key-heistReleases · bitwarden/server · GitHub
https://github.com/bitwarden/server/releases#release-v2026.6.0[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/7615commit dcf4c486b2b5 (bitwarden/server)
Patch available: bitwarden/server v2026.6.0 (contains commit dcf4c486b2b5)
https://github.com/bitwarden/server/commit/dcf4c486b2b5bedecc03a48b427243328cc74a9aWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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.
- 2026-07-08 19:46 UTCEG score recompute
- 2026-07-08 19:44 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-60104?
When was CVE-2026-60104 disclosed?
What is the CVSS score of CVE-2026-60104?
How do I remediate CVE-2026-60104?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-60104
Is Your Infrastructure Affected by CVE-2026-60104?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.