Keycloak has debug default bind address
Published Nov 13, 2025 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
Keycloak has debug default bind address
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
A vulnerability exists in Keycloak's server distribution where enabling debug mode (`--debug`) insecurely defaults to binding the Java Debug Wire Protocol (JDWP) port to all network interfaces (`0.0.0.0`). This exposes the debug port to the local network, allowing an attacker on the same network segment to attach a remote debugger and achieve remote code execution within the Keycloak Java virtual machine.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- RHSA-2025:21370 ↗
- RHSA-2025:21371 ↗
- access.redhat.com ↗
- RHBZ#2402622 ↗
- Patch commit ↗
- Source repository ↗
Record history
Published Nov 13, 2025 · Last refreshed Nov 3, 2026