Advisory record · GHSA-63v5-26vq-m4vm

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

CVSS 3.1 LowEPSS 0.0042 · 36th percentile

Published by the GitHub Advisory Database at 26 Jan 2026, 21:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.keycloak:keycloak-servicesMaven<=26.5.2No fixed version yet
Identifiers
GHSA-63v5-26vq-m4vm · CVE-2026-1190
Weakness (CWE)
CWE-112 · CWE-347 · CWE-613
Published
26 Jan 2026
Updated
10 Sept 2026

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.

Written 2 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:18 UTC First seen by agentprime
  2. 31 Oct 2026, 14:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.