CVE-2024-10451 json
Org.keycloak:keycloak-quarkus-server: sensitive data exposure in keycloak build process
published 2024-11-25 23 mo ago modified 2026-10-13 26 d ago also GHSA-v7gv-xpgf-6395 , EUVD-2024-3384
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.keycloak:keycloak-quarkus-server 24.0.9, 26.0.6
- Red Hat Red Hat build of Keycloak 24 24-18, 24.0.9-1
- Red Hat Red Hat build of Keycloak 26.0 26.0-5, 26.0-6, 26.0.6-2
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-10451 updated cvss 5.9
org.keycloak:keycloak-quarkus-server: Sensitive Data Exposure in Keycloak Build Process
-
Red Hat Single Sign-On 7 keycloak-quarkus-serveraffected: workaround, no fix planned “Out of support scope”
-
Red Hat build of Keycloak 24 rhbk/keycloak-rhel9 24-18, rhbk/keycloak-rhel9-operator 24-18, rhbk/keycloak-operator-bundle 24.0.9-1fixed: vendor fix RHSA-2024:10175
-
Red Hat build of Keycloak 24.0.9fixed: vendor fix RHSA-2024:10176
-
Red Hat build of Keycloak 26.0 rhbk/keycloak-rhel9 26.0-5, rhbk/keycloak-rhel9-operator 26.0-6, rhbk/keycloak-operator-bundle 26.0.6-2fixed: vendor fix RHSA-2024:10177
-
Red Hat build of Keycloak 26.0.6fixed: vendor fix RHSA-2024:10178
-
Red Hat JBoss Enterprise Application Platform 8 keycloak-quarkus-servernot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.keycloak:keycloak-quarkus-server | <24.0.9 >=25.0.0, <26.0.6 |
24.0.9 26.0.6 |
Affected products
- Red Hat Red Hat build of Keycloak 24
- Red Hat Red Hat build of Keycloak 24.0.9
- Red Hat Red Hat build of Keycloak 26.0
- Red Hat Red Hat build of Keycloak 26.0.6
- Red Hat Red Hat JBoss Enterprise Application Platform 8
- Red Hat Red Hat Single Sign-On 7
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
github.com
/keycloak/keycloak/commit/198214310eb45b86707f823ccb5a2d65c814b528
web
-
access.redhat.com
/errata/RHSA-2024:10175
vendor-advisory, web
-
access.redhat.com
/errata/RHSA-2024:10176
vendor-advisory, web
-
access.redhat.com
/errata/RHSA-2024:10177
vendor-advisory, web
-
access.redhat.com
/errata/RHSA-2024:10178
vendor-advisory, web
-
access.redhat.com
/security/cve/CVE-2024-10451
vdb-entry, web
-
bugzilla.redhat.com
/show_bug.cgi?id=2322096
issue-tracking, web
-
github.com
/keycloak/keycloak/security/advisories/GHSA-v7gv-xpgf-6395
web
-
nvd.nist.gov
/vuln/detail/CVE-2024-10451
advisory
-
github.com
/keycloak/keycloak
package
Sources
- CVE List CVE-2024-10451
- GitHub Advisory GHSA-v7gv-xpgf-6395
- NVD CVE-2024-10451
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.