dbcve.org
VaultwardenApplication · Dani Garcia

CVE-2026-27801

MEDIUM · 5.9 CVSS v3.1 Published 2026-03-04
Fix available
A fix is available. Upgrade to 1.35.0 or later.
See remediation →
65/100
Remediation priority · Elevated
Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vaultwarden is an unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs. Vaultwarden versions 1.34.3 and prior are susceptible to a 2FA bypass when performing protected actions. An attacker who gains authenticated access to a user’s account can exploit this bypass to perform protected actions such as accessing the user’s API key or deleting the user’s vault and organisations the user is an admin/owner of . This issue has been patched in version 1.35.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VaultwardenApplication
Affected:< 1.35.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.35.0 or later
Fixed in 1.35.0
Recommended fix High confidence

Vaultwarden version 1.35.0

  1. 1. Back up your Vaultwarden data directory and any configuration files before proceeding with the upgrade.
  2. 2. Identify your current deployment method (Docker, binary, or system package).
  3. 3. If using Docker, pull the latest Vaultwarden image: docker pull vaultwarden/server:latest or specifically vaultwarden/server:1.35.0
  4. 4. Stop the running Vaultwarden container or service.
  5. 5. For Docker deployments, recreate the container with the new image version: docker run -d --name vaultwarden -v /vw-data:/data vaultwarden/server:1.35.0
  6. 6. For binary deployments, download Vaultwarden 1.35.0 from the official GitHub releases page (github.com/dani-garcia/vaultwarden/releases) and replace the existing binary.
  7. 7. Verify the upgrade by checking the Vaultwarden admin page or logs for successful startup.
  8. 8. Test that 2FA protection is now properly enforced for sensitive actions like API key access and vault deletion.
Caveat Review the release notes for 1.35.0 to confirm no configuration changes are required; minor version upgrades typically do not introduce breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27801 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27801 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data