Vulnerability in Bitwarden Server (CVE-2026-60104)
Summary
Vulnerability in Bitwarden Server (CVE-2026-60104). Confidential information can be exposed externally. Exploitable via POST /auth-requests/admin-request.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-60104 has been found in Bitwarden Server.
Attackers can target a specific entry point like POST /auth-requests/admin-request over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Bitwarden Server CVE-2026-60104" on the vendor's site.
CVE-2026-60104 (Bitwarden Server) — CWE-639 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: POST /auth-requests/admin-request
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in Bitwarden Server. Attackers reach the vulnerable code path via POST /auth-requests/admin-request.
Check the vendor advisory for the affected versions of Bitwarden Server. Attack surface: POST /auth-requests/admin-request.
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /auth-requests/admin-request requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Bitwarden Server を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /auth-requests/admin-request' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /auth-requests/admin-requestへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /auth-requests/admin-request on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory disclosure@vulncheck.com
- exploit disclosure@vulncheck.com
- patch disclosure@vulncheck.com
- patch disclosure@vulncheck.com
- web nvd.nist.gov
- web disclosure@vulncheck.com
- web github.com