Advisory record · GHSA-72vp-xfrc-42xm

Keycloak path traversal vulnerability in redirection validation

CVSS 8.1 HighEPSS 0.016 · 75th percentile

Published by the GitHub Advisory Database at 17 Apr 2024, 18:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.keycloak:keycloak-servicesMaven<22.0.10 || >=23.0.0, <24.0.322.0.10, 24.0.3
Identifiers
GHSA-72vp-xfrc-42xm · CVE-2024-1132
Weakness (CWE)
CWE-22
Published
17 Apr 2024
Updated
10 Sept 2026

Machine-written summary

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

Keycloak (org.keycloak:keycloak-services, Maven) versions below 22.0.10, and versions 23.0.0 up to but not including 24.0.3, are affected. An attacker can craft a malicious redirect request that bypasses URL validation, letting them reach other URLs within the domain and possibly sensitive information or conduct further attacks; this affects clients that use a wildcard in their Valid Redirect URIs. Upgrade to 22.0.10 or 24.0.3. The source gives few details on other workarounds.

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

Timeline

  1. 17 Apr 2024, 13:17 UTC Published by the maintainers as a GitHub repository advisory
  2. 17 Apr 2024, 13:21 UTC Confirmed by the CVE List
  3. 17 Apr 2024, 14:15 UTC Confirmed by NVD
  4. 31 Oct 2026, 14:17 UTC First seen by agentprime
  5. 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.