Keycloak has debug default bind address

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.8 · CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2025-11538: 0.43% estimated exploitation activity in the next 30 days; percentile 36.78 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. Red Hat evaluates this as a Moderate impact vulnerability due to the requirement of running debug mode and untrusted network. Also, for Red Hat Single Sign-On, this must as well be bound to 0.0.0.0 address, which is not recommended in production scenarios.

Published by the source

2 Dec 2025, 00:35 UTC

Last modified by the source

2 Dec 2025, 00:35 UTC

Source last checked

26 Oct 2026, 16:41 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j4vq-q93m-4683

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-11538

Advisory: Keycloak has debug default bind address
IDs: CVE-2025-11538, GHSA-j4vq-q93m-4683
Record: https://patchnext.com/advisories/cve-2025-11538 (revision 1, source checked 26 Oct 2026, 16:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.keycloak:keycloak-quarkus-dist 26.4.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.keycloak:keycloak-quarkus-dist: affected < 26.4.4; fixed in 26.4.4

## Suggested inspection (read-only)
- Maven org.keycloak:keycloak-quarkus-dist: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.keycloak:keycloak-quarkus-dist.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j4vq-q93m-4683 (GitHub-reviewed advisory GHSA-j4vq-q93m-4683 lists affected ranges: Maven org.keycloak:keycloak-quarkus-dist >=0 <26.4.4)

Commands are suggestions: review each one before running it.