Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

GHSA-72vp-xfrc-42xm — keycloak-services

HIGH

GHSA-72vp-xfrc-42xm is a high-severity (CVSS 8.1) Path Traversal vulnerability in org.keycloak:keycloak-services. A fix is available for org.keycloak:keycloak-services — see the affected versions and patch details below.

Keycloak path traversal vulnerability in redirection validation

Also known asCVE-2024-1132
Published
Apr 17, 2024
Updated
Sep 10, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-72vp-xfrc-42xm.

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-72vp-xfrc-42xm by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
☕org.keycloak:keycloak-services☕org.keycloak:keycloak-services

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in Keycloak, where it does not properly validate URLs included in a redirect. An attacker can use this flaw to construct a malicious request to bypass validation and access other URLs and potentially sensitive information within the domain or possibly conduct further attacks. This flaw affects any client that utilizes a wildcard in the Valid Redirect URIs field.

Acknowledgements:

Special thanks to Axel Flamcourt for reporting this issue and helping us improve our project.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-servicesall versions22.0.10org.keycloak:keycloak-services:22.0.10
☕Mavenorg.keycloak:keycloak-services≥ 23.0.0&&< 24.0.324.0.3org.keycloak:keycloak-services:24.0.3

Affected Products

10 products · 16 configurations
Application
build of keycloakredhat
all
Application
jboss middleware text-only advisoriesredhat
1 version
1.0
Application
keycloakredhat
≥ 23.0.0 && < 24.0.3
range
Application
migration toolkit for applicationsredhat
1 version
1.0
Application
migration toolkit for runtimesredhat
all
Application
openshift container platformredhat
2 versions
4.114.12

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-services, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.keycloak:keycloak-services to 22.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-72vp-xfrc-42xm is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat Build of Quarkus is not impacted as this CVE affects the server-side Keycloak execution, but Quarkus only acts as a Keycloak client in its quarkus-keycloak-authorization extension. For this reason, Quarkus is marked as having a Low impact.

Workaround published by Red Hat
No current mitigation is available for this vulnerability.
Source: Red Hat security advisory for GHSA-72vp-xfrc-42xm (CC BY 4.0)
ProductFixed inAdvisory
Migration Toolkit for Runtimes 1 on RHEL 8mtr/mtr-operator-bundle:1.2-23RHSA-2024:3919
MTA-6.2-RHEL-9mta/mta-windup-addon-rhel9:6.2.3-2RHSA-2024:3989
Red Hat AMQ Broker 7see advisoryRHSA-2024:3752
Red Hat AMQ Broker 7keycloakRHSA-2024:3762
Red Hat AMQ Broker 7see advisoryRHSA-2024:2945
Red Hat build of Keycloak 22rhbk/keycloak-operator-bundle:22.0.10-1RHSA-2024:1867
Red Hat build of Keycloak 22.0.10keycloakRHSA-2024:1868
Red Hat Single Sign-On 7.6 for RHEL 7rh-sso7-keycloak-0:18.0.13-1.redhat_00001.1.el7ssoRHSA-2024:1860

Frequently Asked Questions

A flaw was found in Keycloak, where it does not properly validate URLs included in a redirect. An attacker can use this flaw to construct a malicious request to bypass validation and access other URLs and potentially sensitive information within the domain or possibly conduct further attacks. This flaw affects any client that utilizes a wildcard in the Valid Redirect URIs field. #### Acknowledgements: Special thanks to Axel Flamcourt for reporting this issue and helping us improve our project.
O3 Security · Impact-Aware SCA

Is GHSA-72vp-xfrc-42xm in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
GHSA-72vp-xfrc-42xm: keycloak (High 8.1) | O3 Security