Account takeover via OAuth state fixation
Published Jul 15, 2026 · Updated Jul 15, 2026
CSRF in Vaultwarden before 1.36.0 allows remote attackers to take over SSO accounts by fixating an OAuth authorization flow. The /connect/authorize endpoint accepts attacker-chosen state and PKCE values without browser-session binding, while failed exchanges leave the keyed SsoAuth record reusable. SSO must be enabled and a victim must follow the IdP link or have an active IdP session; account 2FA blocks final session issuance.
Summary
What happened
CSRF in Vaultwarden before 1.36.0 allows remote attackers to take over SSO accounts by fixating an OAuth authorization flow. The /connect/authorize endpoint accepts attacker-chosen state and PKCE values without browser-session binding, while failed exchanges leave the keyed SsoAuth record reusable. SSO must be enabled and a victim must follow the IdP link or have an active IdP session; account 2FA blocks final session issuance.
The record
- CVE
- CVE-2026-47158
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- Dani Garcia
- Product
- Vaultwarden
- Classifications
- CWE-352, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.36.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo