VulnWatch by ve1ve2
medium 6.9 EPSS 0.47%

GHSA-hxqh-ff5p-wfr3 / CVE-2026-47159: Authentication Flow Information Disclosure in SSO Discovery Allows Organization Enumeration and Pre-Validation Token Exposure

Source:
Vaultwarden releases + advisories (GitHub dani-garcia/vaultwarden)
Published:
Fetched:
Updated:
Affects:
dani-garcia vaultwarden

https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-hxqh-ff5p-wfr3 ↗

repo-advisorysecurityrepo:dani-garcia/vaultwarden

Authentication Flow Information Disclosure in SSO Discovery Allows Organization Enumeration and Pre-Validation Token Exposure ### Summary I identified an issue in Vaultwarden’s SSO discovery / pre-validation flow that may allow an attacker to enumerate SSO-enabled organizations for an arbitrary email address and then obtain a valid pre-validation JWT using only the returned organizationIdentifier, without proving ownership of the supplied email address first. ### Details In the tested flow, the application first accepts an arbitrary email address and returns organization-related SSO metadata, including organizationIdentifier values. Then, using one of these identifiers in the pre-validation request, the server returns a JWT token that appears to be used to continue the SSO process. This behavior may introduce two security problems: 1. Information disclosure / user-org enumeration An attacker can submit arbitrary email addresses and learn whether they are associated with one or more SSO-enabled organizations. 2. Improper access control in SSO pre-validation An attacker can request a pre-validation token using only the discovered organizationIdentifier, before any proof that they control the email identity involved in the first step. Depending on the intended design, this may enable SSO flow abuse, tenant discovery, targeted phishing facilitation, and possible authentication workflow bypass primitives ### PoC **1: Submit arbitrary email to SSO verification endpoint** **Observed response**: The server returns a 200 OK response containing organization data associated with the supplied email, for example: **This discloses:** 1. whether the email is recognized in the SSO/org flow 2. organization names 3. organization identifiers 4. relationship between a target email and one or more organizations This can expose internal organization metadata tied to arbitrary users and may provide an attacker with a trusted token used in the SSO initiation flow without first verifying identity ownership. **Step 2: Use returned organizationIdentifier in pre-validation** **Expected Result** The application should not disclose organization membership / SSO association details for arbitrary email addresses before verifying the requester is authorized to learn that information. Additionally, the pre-validation endpoint should not issue a token solely based on a user-controlled organizationIdentifier that was previously disclosed through a public-facing discovery endpoint. **Actual Result** The system: accepts any supplied email address, returns organization-related SSO metadata, allows the caller to use the returned organizationIdentifier to obtain a pre-validation JWT ### Security Impact **Information Disclosure** An attacker can enumerate whether arbitrary Affected packages: :vaultwarden Patched: vaultwarden 1.36.0

Linked vulnerabilities (2)

Authentication Flow Information Disclosure in SSO Discovery Allows Organization Enumeration and Pre-Validation Token Exposure

Aliases: CVE-2026-47159
CVE-2026-47159 medium 6.9 EPSS 0.47% (p41) NVDCVE.orgGHSA
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

Authentication Flow Information Disclosure in SSO Discovery Allows Organization Enumeration and Pre-Validation Token Exposure

CWE: CWE-287Aliases: GHSA-hxqh-ff5p-wfr3NVD: Deferred