CVE-2025-46815: ZITADEL Allows IdP Intent Token Reuse

Published May 6, 2025
·
Updated

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 security@zitadel.com

Credits

Thanks to Józef Chraplewski from Nedap for reporting this vulnerability.

Other sources

The identity infrastructure software 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, prior to versions 3.0.0, 2.71.9, and 2.70.10, 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. Versions 3.0.0, 2.71.9, and 2.70.10 contain a fix for the issue. No known workarounds other than upgrading are available.

— MITRE

Affected Software

8 affected componentsFixes available
go/github.com/zitadel/zitadel>=2.71.0<=2.71.8
2.71.9
go/github.com/zitadel/zitadel<2.70.10
2.70.10
go/github.com/zitadel/zitadel>=3.0.0-rc.1<=3.0.0-rc.3
3.0.0
ZITADEL ZITADEL<2.70.10
ZITADEL ZITADEL>=2.71.0<2.71.9
ZITADEL ZITADEL=3.0.0-rc1
ZITADEL ZITADEL=3.0.0-rc2
ZITADEL ZITADEL=3.0.0-rc3

Event History

May 6, 2025
Advisory Published
via GitHub·04:51 PM
CVE Published
via MITRE·05:13 PM
Data Sourced
via MITRE·05:13 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
RemedyAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-46815?

CVE-2025-46815 is classified as a medium severity vulnerability impacting user session management.

2

How do I fix CVE-2025-46815?

To mitigate CVE-2025-46815, upgrade ZITADEL to version 2.71.9, 2.70.10, or 3.0.0.

3

Which versions of ZITADEL are affected by CVE-2025-46815?

CVE-2025-46815 affects ZITADEL versions from 2.71.0 to 2.71.8 and below 2.70.10, as well as pre-release versions of 3.0.0.

4

What does CVE-2025-46815 affect?

CVE-2025-46815 affects the ZITADEL Session API, specifically the management of user sessions using IdPs.

5

Are there any public references for CVE-2025-46815?

Yes, CVE-2025-46815 is documented in GitHub advisories and includes specific remediation instructions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203