# CVE-2026-56667: ZITADEL: Stored XSS via Default URI Redirect in Login V2

> An administrator can store malicious URIs that execute JavaScript in users' browsers during login errors, enabling session hijacking or account takeover.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-5wcj-9wj4-j65h

## What is CVE-2026-56667?

CVE-2026-56667 is a high-severity cross-site scripting vulnerability in zitadel, published on 10 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

ZITADEL is an open source identity management platform. Prior to 4.15.3, ZITADEL Login V2 OIDC and SAML FailedPrecondition error paths return loginSettings.defaultRedirectUri to router.push without applying the isSafeRedirectUri check, allowing an organization or instance administrator to store a javascript or data URI that can execute in a user's browser when an affected login error path is reached. This issue is fixed in version 4.15.3.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-56667?


## How do I fix CVE-2026-56667?

No fix has been published for CVE-2026-56667 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56667 being exploited?

There is no known exploitation of CVE-2026-56667 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56667 and fix it if it is affected.

What it is: CVE-2026-56667 is a high-severity cross-site scripting vulnerability in zitadel, published on 10 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-56667 in the wild and no public exploit code.

Affected product: zitadel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56667/ (Markdown: https://insights.sbomify.com/CVE-2026-56667/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56667
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56667
- OSV: https://osv.dev/vulnerability/CVE-2026-56667

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56667/
Summaries are generated and may contain mistakes; the official description above is the record.