LOW3.1

GHSA-63v5-26vq-m4vm

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

Details

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.

Are you affected?

Enter the version of the package you're using.

Affected packages

Maven/org.keycloak:keycloak-services

Introduced in: 0

No fixed version published yet for org.keycloak:keycloak-services (maven). Pin to a known-safe version or switch to an alternative.

References

https://nvd.nist.gov/vuln/detail/CVE-2026-1190[ADVISORY]
https://github.com/keycloak/keycloak/issues/45646[WEB]
https://access.redhat.com/errata/RHSA-2026:3947[WEB]
https://access.redhat.com/errata/RHSA-2026:3948[WEB]
https://access.redhat.com/security/cve/CVE-2026-1190[WEB]
https://bugzilla.redhat.com/show_bug.cgi?id=2430835[WEB]
https://github.com/keycloak/keycloak[WEB]