# CVE-2024-10451: Org.keycloak:keycloak-quarkus-server: sensitive data exposure in keycloak build process

> Sensitive runtime values like passwords are embedded in bytecode during the build process, allowing attackers to access them at runtime.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Nov 2024
- **Updated:** 13 Oct 2026
- **Also known as:** ECHO-fea2-5ea1-2849, GHSA-v7gv-xpgf-6395

## What is CVE-2024-10451?

CVE-2024-10451 is a medium-severity vulnerability in Red Hat JBoss Enterprise Application Platform 8, published on 25 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in Keycloak. This issue occurs because sensitive runtime values, such as passwords, may be captured during the Keycloak build process and embedded as default values in bytecode, leading to unintended information disclosure. In Keycloak 26, sensitive data specified directly in environment variables during the build process is also stored as a default values, making it accessible during runtime. Indirect usage of environment variables for SPI options and Quarkus properties is also vulnerable due to unconditional expansion by PropertyMapper logic, capturing sensitive data as default values in all Keycloak versions up to 26.0.2.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2024-10451?

4 open source packages ship an affected version, including org.keycloak:keycloak-quarkus-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-quarkus-server` | Maven | All versions | 24.0.9 |
| `org.keycloak:keycloak-quarkus-server` | Maven | All versions | 24.0.9 |
| `org.keycloak:keycloak-quarkus-server` | Maven | From 25.0.0 | 26.0.6 |
| `org.keycloak:keycloak-quarkus-server` | Maven | From 25.0.0 | 26.0.6 |

## How do I fix CVE-2024-10451?

Upgrade org.keycloak:keycloak-quarkus-server to a fixed version for your release line: 24.0.9 or 26.0.6.

## Is CVE-2024-10451 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10451 and fix it if it is affected.

What it is: CVE-2024-10451 is a medium-severity vulnerability in Red Hat JBoss Enterprise Application Platform 8, published on 25 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10451 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-quarkus-server (Maven): affected all versions; fixed in 24.0.9
- org.keycloak:keycloak-quarkus-server (Maven): affected all versions; fixed in 24.0.9
- org.keycloak:keycloak-quarkus-server (Maven): affected from 25.0.0; fixed in 26.0.6
- org.keycloak:keycloak-quarkus-server (Maven): affected from 25.0.0; fixed in 26.0.6

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

## Sources

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

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