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

> An authenticated attacker can inject forged audit log entries into any organization's logs due to missing membership verification.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-m2wp-hqw2-j56m, MINI-3rcv-q6r8-6cf7

## What is CVE-2026-71959?

CVE-2026-71959 is a medium-severity missing authorization vulnerability in bitwarden server, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-71959?


## How do I fix CVE-2026-71959?

Upgrade to a fixed version.

## Is CVE-2026-71959 being exploited?

There is no known exploitation of CVE-2026-71959 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71959 and fix it if it is affected.

What it is: CVE-2026-71959 is a medium-severity missing authorization vulnerability in bitwarden server, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71959 in the wild and no public exploit code.

Affected product: bitwarden server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71959/ (Markdown: https://insights.sbomify.com/CVE-2026-71959/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71959
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71959
- OSV: https://osv.dev/vulnerability/CVE-2026-71959

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71959/
Summaries are generated and may contain mistakes; the official description above is the record.