CVE-2026-43913: Vaultwarden: Unconfirmed Owner Can Purge Entire Organization Vault
Vaultwarden is a Bitwarden-compatible server written in Rust. Prior to 1.35.5, Vaultwarden allows an unconfirmed organization owner to purge the entire organization vault. The organization invite flow uses a two-step process: accepting an invite transitions membership from Invited to Accepted, and a separate confirmation by an existing owner upgrades it to Confirmed. The POST /api/ciphers/purge endpoint uses plain Headers and only checks that the membership type is Owner without verifying that the membership status is Confirmed. An authenticated user who has been invited as an organization owner and has accepted the invite and has not yet been confirmed can call this endpoint to hard-delete all ciphers and attachments in the organization, causing immediate organization-wide data loss. This vulnerability is fixed in 1.35.5.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43913?
CVE-2026-43913 has a high severity rating due to the potential for unconfirmed organization owners to purge the entire vault.
How do I fix CVE-2026-43913?
To fix CVE-2026-43913, upgrade Vaultwarden to version 1.35.5 or later.
What systems are affected by CVE-2026-43913?
CVE-2026-43913 affects all versions of Vaultwarden prior to 1.35.5.
Can an unconfirmed owner delete vault data in CVE-2026-43913?
Yes, an unconfirmed organization owner can purge the entire organization vault due to this vulnerability.
Is it safe to use Vaultwarden versions prior to 1.35.5 with CVE-2026-43913?
Using Vaultwarden versions prior to 1.35.5 is not safe due to the risks posed by CVE-2026-43913.