Service interruption via proxy-header DNS resolution
Published Nov 25, 2024 · Updated Aug 31, 2026
Denial of service in Keycloak before 24.0.9 and 25.0.0 through 26.0.5 allows attackers to exhaust I/O threads via proxy headers. The proxy-header parser accepts non-IP values such as obfuscated identifiers as client addresses and performs costly DNS resolution on them. Exploitation requires accepted proxy headers, a reverse proxy that does not overwrite attacker-supplied values, and, for version 26, HTTP plus the documented hostname and trust conditions.
Summary
What happened
Denial of service in Keycloak before 24.0.9 and 25.0.0 through 26.0.5 allows attackers to exhaust I/O threads via proxy headers. The proxy-header parser accepts non-IP values such as obfuscated identifiers as client addresses and performs costly DNS resolution on them. Exploitation requires accepted proxy headers, a reverse proxy that does not overwrite attacker-supplied values, and, for version 26, HTTP plus the documented hostname and trust conditions.
The record
- CVE
- CVE-2024-9666
- Published
- Nov 25, 2024
- Updated
- Aug 31, 2026
- Vendor
- Red Hat
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-444, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 25, 2024CVE publishedPublication date reported by the CVE source.
- Aug 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo