Keycloak's missing timestamp validation allows attackers to extend SAML response validity periods
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-1190US | — | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:3947WEB
- https://access.redhat.com/errata/RHSA-2026:3948WEB
- https://access.redhat.com/security/cve/CVE-2026-1190WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2430835WEB
- https://github.com/keycloak/keycloakWEB
- https://github.com/keycloak/keycloak/issues/45646WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-1190ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan