Keycloak's missing timestamp validation allows attackers to extend SAML response validity periods
Low severity
GitHub Reviewed
Published
Jan 26, 2026
to the GitHub Advisory Database
•
Updated Jan 27, 2026
Description
Published by the National Vulnerability Database
Jan 26, 2026
Published to the GitHub Advisory Database
Jan 26, 2026
Reviewed
Jan 27, 2026
Last updated
Jan 27, 2026
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
NotOnOrAftertimestamp within theSubjectConfirmationData. 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