Home

Description

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.

PUBLISHED Reserved 2026-01-19 | Published 2026-01-26 | Updated 2026-01-26 | Assigner redhat




LOW: 3.1CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

Problem types

Missing XML Validation

Product status

Default status
affected

Default status
affected

Default status
affected

Default status
affected

Timeline

2026-01-19:Reported to Red Hat.
2026-01-19:Made public.

Credits

Red Hat would like to thank Franz Bettag (Bettag Systems) for reporting this issue.

References

access.redhat.com/security/cve/CVE-2026-1190 vdb-entry

bugzilla.redhat.com/show_bug.cgi?id=2430835 (RHBZ#2430835) issue-tracking

cve.org (CVE-2026-1190)

nvd.nist.gov (CVE-2026-1190)

Download JSON