dbcve.org
VaultwardenApplication · Dani Garcia

CVE-2026-33420

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-05
Fix available
A fix is available. Upgrade to 1.35.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 a Bitwarden-compatible server written in Rust. In version 1.35.4 and earlier, the get_org_collections_details endpoint (GET /api/organizations/{org_id}/collections/details) is missing the has_full_access() authorization check that exists on the sibling get_org_collections endpoint. This allows any Manager-role user with accessAll=False and no collection assignments to retrieve the names, UUIDs, user-to-collection mappings, and group-to-collection mappings for all collections in the organization. This issue has been fixed in version 1.35.5.

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

Vaultwarden versions 1.35.4 and earlier lack an authorization check (has_full_access()) on the GET /api/organizations/{org_id}/collections/details endpoint. This allows Manager users with accessAll=False and no collection assignments to bypass intended access controls and retrieve sensitive organization data including collection names, UUIDs, and user/group-to-collection mappings.

MitigationUpgrade Vaultwarden to version 1.35.5 or later to apply the missing authorization check.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Vaultwarden version via the admin interface, docker image tag, or package manager. If using the web vault, the version is often displayed in the footer of the admin page.
    Affected if Version is 1.35.4 or earlier
  2. Verify organization exists
    Confirm you have organizations configured in Vaultwarden by logging into the web vault and checking for the 'Organizations' section, or by querying the API at /api/organizations
    Affected if At least one organization is present
  3. Identify Manager role users
    Query the API endpoint GET /api/organizations/{org_id}/users (replace {org_id} with your organization UUID) and examine the 'type' or 'role' field for users with Manager role
    Affected if Any user has Manager role in the organization
  4. Check Manager user accessAll flag
    Examine the JSON response from /api/organizations/{org_id}/users for Manager users. Look for the 'accessAll' field - if it is set to false and the user has Manager role, they meet the vulnerable condition
    Affected if Manager users exist with accessAll=false and no collection assignments
  5. Test the vulnerable endpoint
    Using a test Manager account (accessAll=false, no collections assigned), make a GET request to /api/organizations/{org_id}/collections/details. If the response returns collection names, UUIDs, and user mappings, the vulnerability is present
    Affected if Endpoint returns collection data without requiring full admin access

You are affected if Vaultwarden version is 1.35.4 or earlier AND your organization has Manager role users with accessAll=false who can retrieve all collection details through the vulnerable 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.5 or later
Fixed in 1.35.5
Interim mitigation

Upgrade Vaultwarden to version 1.35.5 or later to apply the missing authorization check.

Recommended fix High confidence

1.35.5

  1. Ensure you have a backup of your Vaultwarden data and configuration before upgrading
  2. Stop the Vaultwarden service
  3. Upgrade Vaultwarden to version 1.35.5 or later
  4. Verify the service starts successfully
  5. Confirm the upgrade was successful by checking the Vaultwarden version

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

Fix this in Vaultwarden Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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