# Vaultwarden has 2FA Bypass on Protected Actions due to Faulty Rate Limit Enforcement

Advisory record · `GHSA-v6pg-v89r-w8wr`

- **Identifiers:** `GHSA-v6pg-v89r-w8wr` · `CVE-2026-27801`
- **State:** Confirmed
- **Severity:** CVSS 6.0 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-307](https://cwe.mitre.org/data/definitions/307.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 4 Mar 2026
- **Updated:** 5 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Mar 2026, 20:06 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `vaultwarden` (crates.io): affected `<1.35.0`; fixed in `1.35.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Vaultwarden 1.34.3 and earlier, as published on crates.io, let an attacker who already has authenticated access to a user's account bypass the 2FA check on protected actions such as viewing the API key or deleting the vault. The per-code attempt limit is not saved correctly, so an attacker can brute-force the six-digit emailed one-time passcode. Upgrade to version 1.35.0 or later. The source gives few details on other workarounds.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.0 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0029, the 21st percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:19 UTC: First seen by agentprime
- 31 Oct 2026, 15:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-v6pg-v89r-w8wr)

## Sources

- [GitHub Advisory Database: GHSA-v6pg-v89r-w8wr](https://github.com/advisories/GHSA-v6pg-v89r-w8wr)
- [OSV: GHSA-v6pg-v89r-w8wr](https://osv.dev/vulnerability/GHSA-v6pg-v89r-w8wr)
- <https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-v6pg-v89r-w8wr>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-27801>
- <https://github.com/dani-garcia/vaultwarden>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-v6pg-v89r-w8wr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-v6pg-v89r-w8wr/>. Everything for agents: <https://agentprime.io/llms.txt>.
