CVE-2024-10039 — keycloak-core
HIGHCVE-2024-10039 is a high-severity (CVSS 7.1) vulnerability in org.keycloak:keycloak-core. A fix is available for org.keycloak:keycloak-core — see the affected versions and patch details below.
Keycloak mTLS Authentication Bypass via Reverse Proxy TLS Termination
Real-World Exposure
org.keycloak:keycloak-coreReal-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 vulnerability was found in Keycloak. Deployments of Keycloak with a reverse proxy not using pass-through termination of TLS, with mTLS enabled, are affected. This issue may allow an attacker on the local network to authenticate as any user or client that leverages mTLS as the authentication mechanism.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.keycloak:keycloak-core | all versions | 26.0.6org.keycloak:keycloak-core: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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.keycloak:keycloak-core to 26.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-10039 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-10039 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-10039. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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 does not ship the Keycloak server code and thus is not affected by this vulnerability.
| 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 |
| Red Hat Single Sign-On 7 | see advisory | RHSA-2025:11645 |
Frequently Asked Questions
Is CVE-2024-10039 in your dependencies?
O3 Security finds CVE-2024-10039 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.