# CVE-2026-47158: Vaultwarden CSRF and session hijacking in SSO authorization flow

Source: https://junglewise.ai/threats/cve-2026-47158-vaultwarden-csrf-and-session-hijacking-in-sso-authorization-flow  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-15. Updated: 2026-07-15  
License: CC BY 4.0 with a link back

CVE-2026-47158 · Severity: high · CVSS 8.3 · Published 2026-07-15

Vaultwarden, an open-source password management server, contained a security flaw in its Single Sign-On (SSO) login process. An attacker could trick a user into a malicious login flow that allows the attacker to hijack the session and gain access to the user's encrypted vault data. This could lead to the exposure of sensitive passwords and credentials stored within the organization.

## Quick answers

**Is CVE-2026-47158 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-47158 being exploited in the wild.

**How severe is CVE-2026-47158?** High severity, with a CVSS score of 8.3, published 15 July 2026.

**Which products and versions are affected?** dani-garcia Vaultwarden < 1.36.0.

**Is there a fix for CVE-2026-47158?** A patch was published on 2026-04-29: Fixes committed to main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-47158 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-47158?** Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A vulnerability in Vaultwarden's SSO implementation (prior to version 1.36.0) stems from a failure to bind the OAuth 'state' parameter accepted by the /connect/authorize endpoint to the initiating browser session. Additionally, the application allowed attacker-controlled PKCE parameters and failed to invalidate SsoAuth records after unsuccessful token exchanges. An unauthenticated remote attacker can exploit these weaknesses via a Cross-Site Request Forgery (CSRF) vector to induce Identity Provider (IdP) authentication and subsequently redeem tokens for a fully authenticated session. While the master password is still required for full decryption of some data, an attacker can successfully fetch encrypted vault data. The issue is resolved in version 1.36.0 by implementing cookie-based session binding for SSO tokens.

## Affected products

- dani-garcia Vaultwarden < 1.36.0

## Timeline

- 2026-04-29: patched: Fixes committed to main branch
- 2026-05-03: advisory: Release 1.36.0 published with security fixes
- 2026-07-15: disclosed: CVE-2026-47158 published

## References

- [https://github.com/dani-garcia/vaultwarden/commit/d297e274a35dccd0f5d935e9d5934e0f7e9c0a87](https://github.com/dani-garcia/vaultwarden/commit/d297e274a35dccd0f5d935e9d5934e0f7e9c0a87)
- [https://github.com/dani-garcia/vaultwarden/pull/7163](https://github.com/dani-garcia/vaultwarden/pull/7163)
- [https://github.com/dani-garcia/vaultwarden/releases/tag/1.36.0](https://github.com/dani-garcia/vaultwarden/releases/tag/1.36.0)
- [https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-pfp2-jhgq-6hg5](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-pfp2-jhgq-6hg5)