CVE-2026-60104
Bitwarden Server broken access control
- Published8 Jul 2026
Description
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 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:NAffected products
Remediation
References
- https://github.com/bitwarden/server/commit/dcf4c486b2b5bedecc03a48b427243328cc74a9a
- https://github.com/bitwarden/server/pull/7615
- https://github.com/bitwarden/server/releases#release-v2026.6.0
- https://sanjokkarki.com.np/blog/bitwarden-vault-key-heist
- https://www.vulncheck.com/advisories/bitwarden-server-authorization-bypass-via-admin-auth-request
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-60104 being actively exploited?
CVE-2026-60104 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.37%.
How severe is CVE-2026-60104?
CVE-2026-60104 has a CVSS 3.1 base score of 8.7, rated high. EPSS estimates a 0.37% probability of exploitation.
Which products are affected by CVE-2026-60104?
Affected products include Bitwarden Server.
How do I fix CVE-2026-60104?
Upgrade affected software to a fixed version, for example Bitwarden Server 2026.6.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-60104 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.