CVE-2025-46815: ZITADEL Allows IdP Intent Token Reuse
Impact ZITADEL offers developers the ability to manage user sessions using the Session API. This API enables the use of IdPs for authentication, known as idp intents. Following a successful idp intent, the client receives an id and token on a predefined URI. These id and token can then be used to authenticate the user or their session. However, it was possible to exploit this feature by repeatedly using intents.
Published May 6, 2025
Affected packages
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- >= 3.0.0-rc.1, <= 3.0.0-rc.3
- Fixed in
- 3.0.0
- Check
go list -m github.com/zitadel/zitadel
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- < 2.70.10
- Fixed in
- 2.70.10
- Check
go list -m github.com/zitadel/zitadel
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- >= 2.71.0, <= 2.71.8
- Fixed in
- 2.71.9
- Check
go list -m github.com/zitadel/zitadel
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
ZITADEL offers developers the ability to manage user sessions using the Session API. This API enables the use of IdPs for authentication, known as idp intents.
Following a successful idp intent, the client receives an id and token on a predefined URI. These id and token can then be used to authenticate the user or their session.
However, it was possible to exploit this feature by repeatedly using intents. This allowed an attacker with access to the application’s URI to retrieve the id and token, enabling them to authenticate on behalf of the user.
It’s important to note that the use of additional factors (MFA) prevents a complete authentication process and, consequently, access to the ZITADEL API.
Patches
3.x versions are fixed on >=3.0.0 2.71.x versions are fixed on >=2.71.9 2.x versions are fixed on >=2.70.10
Workarounds
The recommended solution is to update ZITADEL to a patched version.
Questions
If you have any questions or comments about this advisory, please email us at [[email protected]](mailto:[email protected])
Credits
Thanks to Józef Chraplewski from Nedap for reporting this vulnerability.
Credited to cfx, livio-a, fforootd.
References
- https://github.com/zitadel/zitadel/security/advisories/GHSA-g4r8-mp7g-85fq
- https://github.com/zitadel/zitadel/commit/b1e60e7398d677f08b06fd7715227f70b7ca1162
- https://github.com/zitadel/zitadel/releases/tag/v2.70.10
- https://github.com/zitadel/zitadel/releases/tag/v2.71.9
- https://github.com/zitadel/zitadel/releases/tag/v3.0.0
- https://nvd.nist.gov/vuln/detail/CVE-2025-46815
- https://github.com/advisories/GHSA-g4r8-mp7g-85fq
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-85056
ZITADEL: MFA bypass via session reuse in Login V2
high8.2Sep 24, 2026CVE-2026-85057
ZITADEL: Actions V1 sandbox escape: host file read via require()
high8.7Sep 24, 2026CVE-2026-56668
ZITADEL: Unauthorized Token Privilege Escalation in OAuth2 Token Exchange
high8.1Sep 14, 2026CVE-2026-76081
ZITADEL: Improper Role Revocation on Granted Projects during Multiple Role Deletions
medium5.5Sep 14, 2026CVE-2026-56665
ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider
medium4.2Sep 11, 2026CVE-2026-56666
ZITADEL: Auto-linking by email: IdP-side email verification is not checked
medium4.8Sep 11, 2026
