Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Keycloak's keycloak-services package, versions up to and including 26.5.2, does not validate the NotOnOrAfter timestamp in SAML SubjectConfirmationData when Keycloak acts as a SAML client. An attacker who can send SAML responses to Keycloak can delay their expiration, extending how long they are accepted and possibly causing unexpected session durations or resource use. The source gives few details on the exact conditions. No fixed version is listed.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 3.1 | Low | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N | CNA (redhat) |
- CISA KEV Not listed.
- EPSS 0.0042, the 36th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:18 UTC First seen by agentprime
- 31 Oct 2026, 14:18 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-63v5-26vq-m4vm
- OSV: GHSA-63v5-26vq-m4vm
- nvd.nist.gov/vuln/detail/CVE-2026-1190
- github.com/keycloak/keycloak/issues/45646
- access.redhat.com/errata/RHSA-2026:3947
- access.redhat.com/errata/RHSA-2026:3948
- access.redhat.com/security/cve/CVE-2026-1190
- bugzilla.redhat.com/show_bug.cgi?id=2430835
- github.com/keycloak/keycloak