dbcve.org
VaultwardenApplication · Dani Garcia

CVE-2026-26012

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 1.35.3 or later.
See remediation →
71/100
Remediation priority · Elevated
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. Prior to 1.35.3, a regular organization member can retrieve all ciphers within an organization, regardless of collection permissions. The endpoint /ciphers/organization-details is accessible to any organization member and internally uses Cipher::find_by_org to retrieve all ciphers. These ciphers are returned with CipherSyncType::Organization without enforcing collection-level access control. This vulnerability is fixed in 1.35.3.

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 · high confidence

In vaultwarden prior to 1.35.3, the /ciphers/organization-details endpoint accessible to any organization member uses Cipher::find_by_org to retrieve all ciphers but returns them with CipherSyncType::Organization without enforcing collection-level access control, allowing regular members to view all organization ciphers regardless of their actual collection permissions.

MitigationUpgrade vaultwarden to version 1.35.3 or later which implements proper collection-level access control enforcement on the affected endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.3

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify vaultwarden version
    Check the running container or binary version using `docker ps` and `docker images` for the vaultwarden image, or run `vaultwarden --version` if using the binary. Alternatively, check the admin dashboard or the response headers for the version string.
    Affected if The installed version is prior to 1.35.3 (e.g., 1.35.2, 1.35.1, 1.35.0, or earlier)
  2. Verify organization feature is in use
    Check if any organization has been created in vaultwarden by logging into the web vault as an admin and viewing the organizations page, or by querying the database for entries in the organizations table.
    Affected if Organizations exist in the vaultwarden instance and the endpoint is accessible to members
  3. Confirm member access to the endpoint
    Log in as a regular (non-admin) organization member and make a request to `/api/sync?excludeDomains=true` or inspect the organization-details endpoint response. A regular member should only see ciphers in collections they have access to.
    Affected if The endpoint returns ciphers that the user does not have collection-level access to, or returns all organization ciphers regardless of collection membership

You are affected if running vaultwarden version prior to 1.35.3 with active organization(s), and a regular organization member can see ciphers outside their assigned collections via the sync or organization-details endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.3 or later
Fixed in 1.35.3
Interim mitigation

Upgrade vaultwarden to version 1.35.3 or later which implements proper collection-level access control enforcement on the affected endpoint.

Recommended fix High confidence

vaultwarden >= 1.35.3

  1. Upgrade vaultwarden to version 1.35.3 or later to resolve the incorrect authorization vulnerability where organization members could access all ciphers regardless of collection permissions

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

Fix this in Vaultwarden Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26012 — 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-26012 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