# CVE-2026-43913: Vaultwarden: Unconfirmed Owner Can Purge Entire Organization Vault

> An unconfirmed organization owner can purge all vault data due to missing status checks, causing immediate data loss.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-937x-3j8m-7w7p

## What is CVE-2026-43913?

CVE-2026-43913 is a high-severity missing authorization vulnerability in dani-garcia vaultwarden, published on 11 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-43913?

It affects 1 product.


Products: Dani-Garcia Vaultwarden.

## How do I fix CVE-2026-43913?

No fix has been published for CVE-2026-43913 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-43913 being exploited?

There is no known exploitation of CVE-2026-43913 in the wild and no public exploit code.

## Other vulnerabilities in dani-garcia vaultwarden

- [CVE-2024-55225](https://insights.sbomify.com/CVE-2024-55225/): Vaultwarden vulnerable to user impersonation (critical 9.8)
- [CVE-2024-55224](https://insights.sbomify.com/CVE-2024-55224/): Vaultwarden HTML injection vulnerability (critical 9.6)
- [CVE-2024-39924](https://insights.sbomify.com/CVE-2024-39924/): Privilege escalation in n/a (high 8.8)
- [CVE-2026-43912](https://insights.sbomify.com/CVE-2026-43912/): Vaultwarden: Cross-Org Group Binding Enables Unauthorized Read And Write Access Into Another Organization (high 8.7)
- [CVE-2026-27802](https://insights.sbomify.com/CVE-2026-27802/): Vaultwarden: Privilege Escalation via Bulk Permission Update to Unauthorized Collections by Manager (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43913 and fix it if it is affected.

What it is: CVE-2026-43913 is a high-severity missing authorization vulnerability in dani-garcia vaultwarden, published on 11 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43913 in the wild and no public exploit code.

Affected product: dani-garcia vaultwarden. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43913/ (Markdown: https://insights.sbomify.com/CVE-2026-43913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43913
- OSV: https://osv.dev/vulnerability/CVE-2026-43913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43913/
Summaries are generated and may contain mistakes; the official description above is the record.