Skip to content
VulniPulse
Advisory severityHigh8.2Red Hat Linux

High [CVE-2025-3501] Org.keycloak.protocol.services: keycloak hostname verification

This high-severity Red Hat Linux advisory covers CVE-2025-3501 affecting Red Hat build of Keycloak 26.0, Red Hat build of Keycloak 26.2.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2025-3501 Source published Source updated

VulniPulse record published

Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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

Red Hat has rated this as an Important severity, although this configuration is not recommended, especially in production environments. Weakness: CWE-297.

Affected Red Hat products: Red Hat Build of Keycloak; Red Hat build of Keycloak 26; Red Hat build of Keycloak 26.0; Red Hat build of Keycloak 26.2. Red Hat lists Red Hat Single Sign-On 7 as not affected.

Red Hat fixing advisory: RHSA-2025:4336, RHSA-2025:8690, RHSA-2025:4335, RHSA-2025:8672.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 21 days ago·verify at source

Fixed versions
  • keycloak
  • rhbk/keycloak-operator-bundle:26.0.11-2
  • rhbk/keycloak-rhel9:26.0-12
  • rhbk/keycloak-rhel9-operator:26.0-13
  • rhbk/keycloak-operator-bundle:26.2.5-1
  • rhbk/keycloak-rhel9:26.2-4
  • rhbk/keycloak-rhel9-operator:26.2-4
  • RHSA-2025:4336
  • RHSA-2025:8690
  • RHSA-2025:4335
  • RHSA-2025:8672

Official advisory · high-confidence parse· fetched 21 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Use the correct TLS configuration and avoid using "--tls-hostname-verifier=any".

Official advisory · high-confidence parse· fetched 21 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.