CVE Vulnerabilities

CVE-2025-3501

Improper Validation of Certificate with Host Mismatch

Published: Apr 29, 2025 | Modified: Apr 15, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
8.2 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Ubuntu
root.io logo minimus.io logo echo.ai logo

A flaw was found in Keycloak. By setting a verification policy to ALL, the trust store certificate verification is skipped, which is unintended.

Weakness

The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.

Affected Software

NameVendorStart VersionEnd Version
Red Hat Build of KeycloakRedHatkeycloak*
Red Hat build of Keycloak 26RedHat*
Red Hat build of Keycloak 26.0RedHatrhbk/keycloak-operator-bundle:26.0.11-2*
Red Hat build of Keycloak 26.0RedHatrhbk/keycloak-rhel9:26.0-12*
Red Hat build of Keycloak 26.0RedHatrhbk/keycloak-rhel9-operator:26.0-13*
Red Hat build of Keycloak 26.2RedHatrhbk/keycloak-operator-bundle:26.2.5-1*
Red Hat build of Keycloak 26.2RedHatrhbk/keycloak-rhel9:26.2-4*
Red Hat build of Keycloak 26.2RedHatrhbk/keycloak-rhel9-operator:26.2-4*

Extended Description

Even if a certificate is well-formed, signed, and follows the chain of trust, it may simply be a valid certificate for a different site than the site that the product is interacting with. In order to ensure data integrity, the certificate must be valid, and it must pertain to the site that is being accessed. Even if the product attempts to check the hostname, it is still possible to incorrectly check the hostname. For example, attackers could create a certificate with a name that begins with a trusted name followed by a NUL byte, which could cause some string-based comparisons to only examine the portion that contains the trusted name.

Potential Mitigations

References