Skip to content
statance
MenuClose
medium · CVSS 6.8

CVE-2026-95503

Keycloak-services: keycloak-services: potential kdc spoofing bypass when kerberos password authentication is enabled

Published 22 Sept 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 10:44 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A flaw was found in the Kerberos federation provider of Keycloak, an open-source identity and access management solution. When Kerberos password authentication is used without SPNEGO, the system fails to verify the identity of the Key Distribution Center (KDC) by requesting a server ticket. This allows an attacker on the same network to spoof the KDC and bypass the authentication process, potentially gaining unauthorized access to user accounts.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
keycloak/rhbk-openshift-rhel9Red HatDefault status: unaffectedSee vendor advisory
keycloak-servicesRed HatDefault status: unaffectedSee vendor advisory
rhbk/keycloak-rhel9Red HatDefault status: unaffectedSee vendor advisory
keycloak-servicesRed HatDefault status: affectedSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed