Skip to main content
VulnerabilityPublished

CVE-2025-11538: Org.keycloak:keycloak quarkus dist: Keycloak has debug default bind address

Affects org.keycloak:keycloak-quarkus-distSource GCVE Database

0
Compare
Authoritative record:CVE-2025-11538· Medium 6.8

Not known to be exploited · CVSS 6.8 Medium : upgrade to 26.4.4 when convenient.

Data as of 21 Nov 2026, 03:46 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 26.4.4
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade org.keycloak:keycloak-quarkus-dist to 26.4.4.

Affected software

ProductAffectedFixed in
Mavenorg.keycloak:keycloak-quarkus-distAffected
  • <26.4.4
Fixed in
  • 26.4.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official security update by upgrading to Keycloak version 26.4.4 or later. Red Hat provides patched packages and container images in advisories RHSA-2025:21370 and RHSA-2025:21371. Before updating, back up existing installations and configurations. Avoid running Keycloak in debug mode in production environments, especially with the debug port bound to all network interfaces.

Description

Keycloak versions prior to 26.4.4 have a vulnerability where enabling debug mode causes the Java Debug Wire Protocol (JDWP) port to bind to all network interfaces (0.0.0.0) by default. This exposes the debug port to the local network, potentially allowing an attacker on the same network segment to attach a remote debugger and execute code within the Keycloak JVM. Red Hat rates this as a Moderate severity issue due to the requirement of debug mode and network access. The issue is fixed in Keycloak version 26.4.4.

References

Community reviews

Loading reviews…