# CVE-2026-95814: Vaultwarden through 1.37.3 Authorization Bypass via Missing Status Check

> Attackers with revoked or pending membership can access, modify, or delete organization cipher data due to missing status checks in Vaultwarden.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-hm7r-36jx-j25q, MINI-m2r3-wrp8-w2r5

## What is CVE-2026-95814?

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

### Official description

Vaultwarden through 1.37.3 omits organization membership status validation from three cipher access-restriction queries, allowing revoked and not-yet-confirmed members to retain read, write, delete, and attachment access to organization ciphers. Attackers with revoked or pending membership can exploit missing status filters in get_user_collections_access_flags, get_group_collections_access_flags, and is_in_full_access_group to access protected cipher data server-side.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Apply the vendor's patch.

## Is CVE-2026-95814 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95814 is a high-severity missing authorization vulnerability in dani-garcia vaultwarden, published on 22 Sep 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-95814 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-95814/ (Markdown: https://insights.sbomify.com/CVE-2026-95814/index.md)
```

## Sources

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

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