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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
Low
Basic privileges needed
User Interaction
Passive
Minimal interaction
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Bitwarden Server
cpe:2.3:a:bitwarden:server:*:*:*:*:*:*:*:*
|
— |
2026.6.0
|
References 5
https://github.com/bitwarden/server/commit/dcf4c486b2b5bedecc03a48b427243328cc7…
disclosure@vulncheck.com
https://github.com/bitwarden/server/pull/7615
disclosure@vulncheck.com
https://github.com/bitwarden/server/releases#release-v2026.6.0
disclosure@vulncheck.com
https://sanjokkarki.com.np/blog/bitwarden-vault-key-heist
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/bitwarden-server-authorization-bypass-via-…
disclosure@vulncheck.com