CVE-2026-71959
Bitwarden Server < 2026.7.2 Audit Log Injection via POST /collect
Bitwarden Server before 2026.7.2 does not verify that the caller is a member of the organization identified in a POST /collect request body, allowing any authenticated user to write forged, arbitrarily backdated entries into any organization's audit log.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: VulnCheckFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: VulnCheckAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| server bitwarden bitwarden/server
github |
≥ 0; < 2026.7.2 (affected, semver)
Other versions: affected |
CNA: VulnCheck |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 6.9 medium |
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N | CNA: VulnCheck |
| 3.1 / 5.8 medium |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N | CNA: VulnCheck |
Exploit evidence
- https://sanjokkarki.com.np/blog/bitwarden-audit-log-forgery
exploit · CNA: VulnCheck
References
- https://sanjokkarki.com.np/blog/bitwarden-audit-log-forgeryCNA: VulnCheck · technical-description, exploit
- https://github.com/bitwarden/server/releases/tag/v2026.7.2CNA: VulnCheck · release-notes
- https://github.com/bitwarden/server/pull/7934CNA: VulnCheck · issue-tracking, patch
- https://github.com/bitwarden/server/commit/2aa92a3c8675a28e305e8207ff16592227f96291CNA: VulnCheck · patch
- https://www.vulncheck.com/advisories/bitwarden-server-audit-log-injection-via-post-collectCNA: VulnCheck · third-party-advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.