# CVE-2026-71959: Bitwarden Server authorization bypass in audit log collection

Source: https://junglewise.ai/threats/cve-2026-71959-bitwarden-server-authorization-bypass-in-audit-log-collection  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-10. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-71959 · Severity: medium · CVSS 5.8 · Published 2026-08-10

Bitwarden Server's audit log endpoint failed to verify that users belonged to an organization before recording events in that organization's log. This allowed any authenticated user to inject forged, backdated audit entries into any organization's audit log—a falsification of security records that could obscure actual unauthorized activity or be used for compliance fraud.

## Quick answers

**Is CVE-2026-71959 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-71959 being exploited in the wild.

**How severe is CVE-2026-71959?** Medium severity, with a CVSS score of 5.8, published 10 August 2026.

**Which products and versions are affected?** Bitwarden Server before 2026.7.2.

**Is there a fix for CVE-2026-71959?** A patch was published on 2026-07-13: Fix merged in commit 2aa92a3c, version 2026.7.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-71959 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-71959?** Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The POST /collect audit logging endpoint accepted four organization event types (Organization_ClientExportedVault, Organization_AutoConfirmEnabled_Admin, Organization_AutoConfirmDisabled_Admin, Organization_InviteLinkClientCopied) without verifying the caller's membership in the target organization. An authenticated user could supply an arbitrary organization ID in the request body and the endpoint would load that organization and log the event without membership checks, allowing injection of backdated entries. The fix adds a GetByOrganizationAsync(organizationId, userId) membership guard that silently drops events from non-members while preserving normal logging for legitimate organization members.

## Affected products

- Bitwarden Server before 2026.7.2

## Timeline

- 2026-08-10: disclosed
- 2026-07-13: patched: Fix merged in commit 2aa92a3c, version 2026.7.2

## References

- [https://github.com/bitwarden/server/commit/2aa92a3c8675a28e305e8207ff16592227f96291](https://github.com/bitwarden/server/commit/2aa92a3c8675a28e305e8207ff16592227f96291)
- [https://github.com/bitwarden/server/pull/7934](https://github.com/bitwarden/server/pull/7934)