CVE-2024-10451 is a medium-severity (CVSS 5.9) Hard-coded Credentials vulnerability in org.keycloak:keycloak-quarkus-server. A fix is available for org.keycloak:keycloak-quarkus-server — see the affected versions and patch details below.
Keycloak Build Process Exposes Sensitive Data
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-10451.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.keycloak:keycloak-quarkus-server☕org.keycloak:keycloak-quarkus-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.keycloak:keycloak-quarkus-server | all versions | 24.0.9org.keycloak:keycloak-quarkus-server:24.0.9 |
| ☕Maven | org.keycloak:keycloak-quarkus-server | ≥ 25.0.0&&< 26.0.6 | 26.0.6org.keycloak:keycloak-quarkus-server:26.0.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-quarkus-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.keycloak:keycloak-quarkus-server to 24.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-10451 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat Enterprise Application Platform 8 does not ship the affected component and so is not affected by this flaw.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.Source: Red Hat security advisory for CVE-2024-10451 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Keycloak 24 | rhbk/keycloak-operator-bundle:24.0.9-1 | RHSA-2024:10175 |
| Red Hat build of Keycloak 24.0.9 | see advisory | RHSA-2024:10176 |
| Red Hat build of Keycloak 26.0 | rhbk/keycloak-operator-bundle:26.0.6-2 | RHSA-2024:10177 |
| Red Hat build of Keycloak 26.0.6 | see advisory | RHSA-2024:10178 |
Frequently Asked Questions
Is CVE-2024-10451 in your dependencies?
Find it across Maven, including transitive dependencies.