~ / search / GHSA-63v5-26vq-m4vm

GHSA-63v5-26vq-m4vm

Keycloak's missing timestamp validation allows attackers to extend SAML response validity periods

Source: GitHub Advisory Database (reviewed) Low CVE-2026-1190

Packages

EcosystemPackageAffectedFixed in
Maven org.keycloak:keycloak-services <= 26.5.2 no fix listed

Details

As written in the advisory (Markdown source, shown as plain text).

A flaw was found in Keycloak's SAML brokering functionality. When Keycloak is configured as a client in a Security Assertion Markup Language (SAML) setup, it fails to validate the `NotOnOrAfter` timestamp within the `SubjectConfirmationData`. This allows an attacker to delay the expiration of SAML responses, potentially extending the time a response is considered valid and leading to unexpected session durations or resource consumption.

References

External links from the advisory. They lead to third-party sites.