Skip to content
Fencer Intel
high 8.2

CVE-2025-3501 json

Org.keycloak.protocol.services: keycloak hostname verification

published last yr. modified last mo. also GHSA-hw58-3793-42gg , EUVD-2025-12660

cvss
8.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits
0
none known

Summary

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

Patch / fix

  • maven org.keycloak:keycloak-services 26.2.2
  • Red Hat Red Hat build of Keycloak 26.0 26.0-12, 26.0-13, 26.0.11-2
  • Red Hat Red Hat build of Keycloak 26.2 26.2-4, 26.2.5-1

Is CVE-2025-3501 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-3501 updated cvss 8.2

org.keycloak.protocol.services: Keycloak hostname verification

  • Red Hat Build of Keycloak
    fixed: vendor fix “Use the correct TLS configuration and avoid using "--tls-hostname-verifier=any".” RHSA-2025:4336
  • Red Hat build of Keycloak 26
    fixed: vendor fix “Use the correct TLS configuration and avoid using "--tls-hostname-verifier=any".” RHSA-2025:8690
  • Red Hat build of Keycloak 26.0 rhbk/keycloak-rhel9 26.0-1745967474, rhbk/keycloak-operator-bundle 26.0.11-2, rhbk/keycloak-rhel9-operator 26.0-1745967472
    fixed: vendor fix “Use the correct TLS configuration and avoid using "--tls-hostname-verifier=any".” RHSA-2025:4335
  • Red Hat build of Keycloak 26.2 rhbk/keycloak-rhel9 26.2-4, rhbk/keycloak-rhel9-operator 26.2-4, rhbk/keycloak-operator-bundle 26.2.5-1
    fixed: vendor fix “Use the correct TLS configuration and avoid using "--tls-hostname-verifier=any".” RHSA-2025:8672
  • Red Hat Single Sign-On 7 rh-sso7-keycloak rh-sso7-keycloak
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
GitHub 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-services
<26.2.2
26.2.2

Affected products

  • Red Hat Red Hat Build of Keycloak
  • Red Hat Red Hat build of Keycloak 26
  • Red Hat Red Hat build of Keycloak 26.0
  • Red Hat Red Hat build of Keycloak 26.2
  • Red Hat Red Hat Single Sign-On 7

Classification

Weakness
  • CWE-297 Improper Validation of Certificate with Host Mismatch

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.