Servers and applications
CVE-2026-47158
CSRF in SSO Authorization Flow
- Severity
- High 8.3
- Published
- 19 May 2026
- Last changed
- 19 May 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 1.35.8
- Exploit chance
- 0.3% in the next 30 daysHigher than 16% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · Needs someone to click or open something
- Attacker can
- Read some data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H- Also known as
- GHSA-pfp2-jhgq-6hg5
- Sources
- Project advisories (GitHub)
Description
A cross-site request forgery / session fixation vulnerability in Vaultwarden's SSO authorization flow allowed an unauthenticated attacker to hijack any SSO user's login and obtain a fully authenticated session, leading to account takeover.
The OAuth state parameter accepted by the authorize endpoint was not bound to the initiating browser session. Combined with a PKCE flow under attacker-controlled parameters and a cleanup gap on failed token exchange, an attacker could pre-create an authorization context, induce a victim to complete IdP authentication against it, and then redeem the resulting tokens themselves.
Three design decisions combined to produce the vulnerability:
- No session binding at /connect/authorize. The endpoint accepted arbitrary client-supplied state and code_challenge values without authentication, cookies, or any other browser-session anchor.
- SsoAuth keyed by the client-supplied state.
Workarounds
- Enforce 2FA for all SSO users. Blocks final session issuance but does not prevent the identity leak or account linking under default signup settings.
- Restrict SSO to known domains via SSO_ALLOWED_ORGS / SIGNUPS_DOMAINS_WHITELIST to limit the targetable user pool.
- Apply rate limits to /connect/authorize and /connect/token at a reverse proxy layer.
Affected software
| Software | Affected versions |
|---|---|
VaultwardenServers and applications · github:dani-garcia/vaultwarden |
|
About Vaultwarden
Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs
- Docker Hub pulls
- 361,463,423Docker Hub, 15 Nov 2026
- GitHub stars
- 70,745GitHub, 15 Nov 2026
- Forks
- 3,457GitHub, 15 Nov 2026
- Latest release
- 1.37.5GitHub, 15 Nov 2026
- Released
- 1 Nov 2026GitHub
- License
- AGPL-3.0GitHub
- First published on GitHub
- 17 Feb 2018GitHub
Vulnerabilities in Vaultwarden
- In our list
- 41
- Published in the last 12 months
- 31
- Critical, last 12 months
- 1
- High, last 12 months
- 8
- Known exploited
- 0
- GHSA-7ccc-c43j-4p36Organization member can move personal items into an organization without collection accessMedium 4.3 28 Oct 2026
- GHSA-69q9-v8p6-xvx3Revoked or unconfirmed organization member retains read and delete access to organization ciphersHigh 8.1 28 Oct 2026
- GHSA-q5x6-grh5-fqgcUnbounded client-declared attachment fileSize causes an out-of-bounds panic that permanently breaks vault sync for every user who can see the cipherMedium 6.5 28 Oct 2026
- GHSA-v576-3wvq-xh3cLoop-carried user_created flag in send_invite deletes a pre-existing user's account and entire vault when an invite e-mail failsMedium 6.8 28 Oct 2026
- GHSA-64mc-4p6f-r7x9Revoked or unconfirmed organization Admin can read cipher audit logsMedium 4.3 28 Oct 2026
- GHSA-qwx4-wcv4-mpcvOrganization Admin can revoke and delete Owners through an Admin-mintable organization API keyLow 3.8 28 Oct 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-47158
- GitHub Advisory Database https://github.com/advisories/GHSA-pfp2-jhgq-6hg5
- github.com https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-pfp2-jhgq-6hg5