Bitwarden Server < 2026.7.2 Audit Log Injection via POST /collect
33Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 6.9epss 0.3%
exploitation probability
0.3%top 78% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
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.
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
Affected products
bitwarden · serverpublic PoCs found — 1
cve_referencesanjokkarki.com.np/blog/bitwarden-audit-log-forgeryunverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
References
https://github.com/bitwarden/server/commit/2aa92a3c8675a28e305e8207ff16592227f96291https://github.com/bitwarden/server/pull/7934https://github.com/bitwarden/server/releases/tag/v2026.7.2https://sanjokkarki.com.np/blog/bitwarden-audit-log-forgeryhttps://www.vulncheck.com/advisories/bitwarden-server-audit-log-injection-via-post-collect