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.
CVE-2026-71959
Score 5.8 from GitHub Security Advisory published 2026-08-10. a secondary CVSS source baseline 5.8; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.8
- EG Score
- 5.8(high)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity58% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
August 10, 2026
Last Modified
August 17, 2026
Advisory Details (5)
Auto-updated Aug 10, 2026Bitwarden Server < 2026.7.2 Audit Log Injection via POST /collect | Advisories | VulnCheck
https://www.vulncheck.com/advisories/bitwarden-server-audit-log-injection-via-post-collectSanjok Karki | Offensive Security Engineer
https://sanjokkarki.com.np/blog/bitwarden-audit-log-forgeryVersion 2026.7.2
Patch available: bitwarden/server v2026.7.2
https://github.com/bitwarden/server/releases/tag/v2026.7.2[PM-38773] Require org membership before logging org audit events via /collect
Fix merged in bitwarden/server PR #7934 on 2026-07-13 — awaiting tagged release
https://github.com/bitwarden/server/pull/7934commit 2aa92a3c8675 (bitwarden/server)
Fix landed in bitwarden/server commit 2aa92a3c8675 — awaiting tagged release
https://github.com/bitwarden/server/commit/2aa92a3c8675a28e305e8207ff16592227f96291Vendor Advisories for CVE-2026-71959(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 24× in last 7d / 34× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 22:15 UTCGHSA enrichment
- 2026-08-19 21:26 UTCEG score recompute
- 2026-08-19 21:25 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:20 UTCEG score recompute
- 2026-08-18 20:19 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 19:28 UTCEG score recompute
- 2026-08-17 19:28 UTCGHSA enrichment
- 2026-08-17 18:36 UTCEG score recompute
- 2026-08-17 18:36 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 18:49 UTCEG score recompute
- 2026-08-16 18:49 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 17:58 UTCEG score recompute
- 2026-08-15 17:58 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 17:10 UTCEG score recompute
- 2026-08-14 17:10 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
Show 9 moreShow fewer
- 2026-08-13 16:54 UTCGHSA enrichment
- 2026-08-12 16:06 UTCEG score recompute
- 2026-08-12 16:06 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 15:18 UTCEG score recompute
- 2026-08-11 15:18 UTCGHSA enrichment
- 2026-08-10 14:29 UTCEG score recompute
- 2026-08-10 14:06 UTCEG score recompute
- 2026-08-10 14:05 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-71959?
When was CVE-2026-71959 disclosed?
Is CVE-2026-71959 actively exploited?
What is the CVSS score of CVE-2026-71959?
How do I remediate CVE-2026-71959?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71959
Is Your Infrastructure Affected by CVE-2026-71959?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.