Advisory record · GHSA-xgfv-xpx8-qhcr

Improper Verification of SAML Responses Leading to Privilege Escalation in Keycloak

CVSS 7.7 HighEPSS 0.020 · 81st percentile

Published by the GitHub Advisory Database at 14 Oct 2024, 20:54 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.keycloak:keycloak-saml-coreMaven<22.0.13 || >=23.0.0, <24.0.8 || >=25.0.0, <25.0.622.0.13, 24.0.8, 25.0.6
Identifiers
GHSA-xgfv-xpx8-qhcr · CVE-2024-8698
Weakness (CWE)
CWE-347
Published
14 Oct 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Keycloak's keycloak-saml-core package, versions before 22.0.13, from 23.0.0 before 24.0.8, and from 25.0.0 before 25.0.6, is affected. The SAML signature validation in the XMLSignatureUtil class decides whether a signature covers the full document or only assertions based on where the signature sits in the XML, not on the Reference element. An attacker who can send crafted SAML responses may bypass validation, which could lead to privilege escalation or impersonation. Upgrade to 22.0.13, 24.0.8, 25.0.6, or a later fixed release.

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
7.7 High 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.020, the 81st percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 14 Oct 2024, 14:17 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:17 UTC First seen by agentprime
  3. 31 Oct 2026, 14:17 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.