What is the CVSS score of CVE-2026-43913?

CVE-2026-43913 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Vaultwarden are affected by CVE-2026-43913?

Vaultwarden versions before 1.35.5 contain an authorization bypass that allows unconfirmed organization owners to permanently delete all stored ciphers and attachments, resulting in complete and…. A patch is available.

How to fix or mitigate CVE-2026-43913?

Within 24 hours, identify all Vaultwarden deployments in your infrastructure and document current versions; prioritize checking for unconfirmed owner-role invitations in the database. Within 7 days, upgrade all affected instances to Vaultwarden 1.35.5 or later and verify the upgrade succeeds. Within 30 days, conduct a security audit of all pending organization owner invitations, revoke unnecessary unconfirmed invitations, and review access logs from affected instances for any suspicious purge requests.

Vaultwarden CVE-2026-43913

EUVD-2026-29341 HIGH

Incorrect Authorization (CWE-863)

2026-05-11 GitHub_M

Hashicorp Authentication Bypass Vaultwarden

8.1

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.1 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

vuln.today AI

8.1 HIGH

Network endpoint, low complexity, requires an accepted org-owner invite so PR:L; destructive hard-delete gives I:H/A:H with no data disclosure (C:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 23, 2026 - 22:34 vuln.today

Patch available

May 11, 2026 - 23:03 EUVD

CVE Published

May 11, 2026 - 22:01 nvd

HIGH 8.1

DescriptionGitHub Advisory

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.

AnalysisAI

Improper authorization in Vaultwarden (self-hosted Bitwarden-compatible server) before 1.35.5 lets an authenticated user who was invited as an organization owner and has accepted-but not yet been confirmed-invoke POST /api/ciphers/purge to hard-delete every cipher and attachment in the organization. The endpoint checks only that membership type is Owner and omits the required Confirmed-status check, enabling irreversible organization-wide data loss. There is no public exploit identified at time of analysis, EPSS is negligible (0.04%), and SSVC records no known exploitation.

Technical ContextAI

Vaultwarden is a lightweight Rust reimplementation of the Bitwarden server API, widely self-hosted as a password/secrets vault. The flaw is a CWE-863 Incorrect Authorization: the organization invite lifecycle has three states (Invited → Accepted → Confirmed), where accepting an invite only proves the user acted on it, and a separate confirmation by an existing owner is what actually grants trusted access. The purge handler builds authorization from plain request Headers and gates solely on membership type Owner, never asserting membership status Confirmed. As a result, the intermediate Accepted-but-unconfirmed state-intended to be powerless-retains destructive owner capability. The single affected package is cpe:2.3:a:dani-garcia:vaultwarden.

RemediationAI

Vendor-released patch: upgrade to Vaultwarden 1.35.5 or later, which adds the missing Confirmed-status check on the purge path; this is the primary and complete fix per advisory GHSA-937x-3j8m-7w7p (https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-937x-3j8m-7w7p). Until the upgrade is applied, reduce exposure by not issuing organization-owner invitations (or promptly confirming/revoking pending owner invites so no account lingers in the Accepted-but-unconfirmed state), and treat unexpected pending owner invites as suspicious; on multi-tenant instances restrict who can create organizations and issue owner invites. As a safety net against the irreversible hard-delete, ensure current, tested backups of the Vaultwarden data store so an org-wide purge can be recovered-note this mitigates impact but does not prevent the deletion itself.