dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-47159

MEDIUM · 6.9 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

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. Prior to 1.36.0, Vaultwarden's SSO discovery and pre-validation flow returned organization-related SSO metadata including organizationIdentifier values for arbitrary email addresses and allowed a valid pre-validation JWT to be obtained with only the discovered identifier, enabling SSO-enabled organization enumeration and authentication workflow abuse. This issue is fixed in version 1.36.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 · high confidence

Vaultwarden versions before 1.36.0 have an insecure SSO discovery endpoint that returns organization-related SSO metadata (including organizationIdentifier values) for arbitrary email addresses without authentication. This allows unauthenticated attackers to enumerate SSO-enabled organizations and obtain valid pre-validation JWTs using only the discovered identifier, enabling authentication workflow abuse.

MitigationUpgrade Vaultwarden to version 1.36.0 or later to remediate the SSO metadata exposure and authentication bypass. If immediate upgrade is not possible, consider restricting access to the SSO discovery endpoints via network-level controls.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 installation and version
    Locate the Vaultwarden instance (typically a Docker container or running binary) and check its version, usually visible on the admin dashboard or via the API version endpoint
    Affected if The installed version is below 1.36.0
  2. Determine if SSO (Single Sign-On) is enabled
    Inspect the Vaultwarden configuration files or environment variables (such as .env or config.yml) for SSO-related settings like sso_enabled, oidc_configuration, or similar SSO provider flags
    Affected if SSO configuration is present and enabled in the Vaultwarden deployment
  3. Test the SSO discovery endpoint for unauthenticated access
    Send an HTTP GET request to the SSO discovery endpoint with an arbitrary email address (e.g., using curl: curl -k https://your-vaultwarden-url/sso/[email protected]) and observe if organization SSO metadata is returned without requiring authentication
    Affected if The endpoint returns organizationIdentifier values or SSO metadata for arbitrary email addresses without any authentication credentials
  4. Verify pre-validation JWT generation
    If the discovery endpoint responds, examine whether the response contains or allows generation of pre-validation JWT tokens using the discovered organizationIdentifier
    Affected if Valid pre-validation JWTs can be obtained without authenticating, using identifiers from the discovery endpoint

A user is affected if Vaultwarden version is below 1.36.0, SSO is enabled, and the SSO discovery endpoint returns organization metadata for unauthenticated requests.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Vaultwarden to version 1.36.0 or later to remediate the SSO metadata exposure and authentication bypass. If immediate upgrade is not possible, consider restricting access to the SSO discovery endpoints via network-level controls.

Recommended fix High confidence

Vaultwarden version 1.36.0

  1. 1. Backup your Vaultwarden data directory and any configuration files before upgrading
  2. 2. If using Docker, pull the latest Vaultwarden image with tag 1.36.0 or later: `docker pull vaultwarden/server:1.36.0`
  3. 3. Stop the currently running Vaultwarden container
  4. 4. Start the new container with the same configuration and mounted volumes
  5. 5. Verify the service is running correctly by accessing the web interface
  6. 6. Test that SSO authentication flows work as expected
Caveat Review release notes for any configuration changes between your current version and 1.36.0; minor version upgrades in Vaultwarden are typically backward compatible

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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