org.keycloak:keycloak-quarkus-server@26.0.4 vulnerabilities

Affected versions of this package are vulnerable to Use of Hard-coded Credentials due to sensitive runtime values being captured during the build process and embedded as default values in bytecode.

Note:

For versions 26.x, sensitive data specified directly in environment variables during the build process is also stored as a default value, making it accessible during runtime. Indirect usage of environment variables for SPI options and Quarkus properties is also vulnerable due to unconditional expansion by PropertyMapper logic, capturing sensitive data as default values.

Upgrade org.keycloak:keycloak-quarkus-server to version 26.0.6 or higher.

Affected versions of this package are vulnerable to HTTP Request Smuggling due to improper handling of proxy headers resulting in costly DNS resolution operations. An attacker could tie up IO threads and potentially cause a denial of service by exploiting these operations.

Notes:

1. This is only exploitable if the attacker has access to send requests to a Keycloak instance that is configured to accept proxy headers, specifically when reverse proxies do not overwrite incoming headers, and Keycloak is configured to trust these headers.

2. For versions 26.x, this is only exploitable if the realm must have SslRequired=EXTERNAL (the default), HTTP must be enabled, the instance must not be using a full hostname URL, access must come from behind a proxy (assuming the proxy overwrites the X-Forwarded-For header), and trusted proxies must not be set or must incorrectly trust the client from which the request is originating.

Upgrade org.keycloak:keycloak-quarkus-server to version 26.0.6 or higher.

Affected versions of this package are vulnerable to Cleartext Transmission of Sensitive Information due to the improper handling of the KC_CACHE_EMBEDDED_MTLS_ENABLED environment option. This option is ignored, causing JGroups configuration for Infinispan clusters to be visible in plain text. An attacker can read sensitive information by accessing adjacent networks related to JGroups.

A fix was pushed into the master branch but not yet published.