# CVE-2025-10044: Keycloak: keycloak error_description injection on error pages

> Attackers can inject misleading text into Keycloak error pages, creating a phishing vector to trick users into contacting malicious actors.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Sep 2025
- **Updated:** 19 Dec 2025
- **Also known as:** ECHO-6c12-d103-6b0a, GHSA-27gc-wj6x-9w55, MINI-37g2-jwj3-36p9

## What is CVE-2025-10044?

CVE-2025-10044 is a medium-severity cross-site scripting vulnerability in Red Hat build of Keycloak 26.0, published on 5 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw was found in Keycloak. Keycloak’s account console and other pages accept arbitrary text in the error_description query parameter. This text is directly rendered in error pages without validation or sanitization. While HTML encoding prevents XSS, an attacker can craft URLs with misleading messages (e.g., fake support phone numbers or URLs), which are displayed within the trusted Keycloak UI. This creates a phishing vector, potentially tricking users into contacting malicious actors.

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

## Which versions are affected by CVE-2025-10044?

8 open source packages ship an affected version, including org.keycloak:keycloak-account-ui and org.keycloak:keycloak-admin-ui.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-account-ui` | Maven | All versions | 26.2.9 |
| `org.keycloak:keycloak-account-ui` | Maven | All versions | 26.2.9 |
| `org.keycloak:keycloak-account-ui` | Maven | From 26.3.0 | 26.3.4 |
| `org.keycloak:keycloak-account-ui` | Maven | From 26.3.0 | 26.3.4 |
| `org.keycloak:keycloak-admin-ui` | Maven | All versions | 26.2.9 |
| `org.keycloak:keycloak-admin-ui` | Maven | All versions | 26.2.9 |
| `org.keycloak:keycloak-admin-ui` | Maven | From 26.3.0 | 26.3.4 |
| `org.keycloak:keycloak-admin-ui` | Maven | From 26.3.0 | 26.3.4 |

## How do I fix CVE-2025-10044?

Upgrade org.keycloak:keycloak-account-ui to a fixed version for your release line: 26.2.9 or 26.3.4.

## Is CVE-2025-10044 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10044 and fix it if it is affected.

What it is: CVE-2025-10044 is a medium-severity cross-site scripting vulnerability in Red Hat build of Keycloak 26.0, published on 5 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-10044 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-account-ui (Maven): affected all versions; fixed in 26.2.9
- org.keycloak:keycloak-account-ui (Maven): affected all versions; fixed in 26.2.9
- org.keycloak:keycloak-account-ui (Maven): affected from 26.3.0; fixed in 26.3.4
- org.keycloak:keycloak-account-ui (Maven): affected from 26.3.0; fixed in 26.3.4
- org.keycloak:keycloak-admin-ui (Maven): affected all versions; fixed in 26.2.9
- org.keycloak:keycloak-admin-ui (Maven): affected all versions; fixed in 26.2.9
- org.keycloak:keycloak-admin-ui (Maven): affected from 26.3.0; fixed in 26.3.4
- org.keycloak:keycloak-admin-ui (Maven): affected from 26.3.0; fixed in 26.3.4

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-2025-10044/ (Markdown: https://insights.sbomify.com/CVE-2025-10044/index.md)
```

## Sources

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

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