# CVE-2024-1132: Keycloak: path transversal in redirection validation > Attackers can bypass redirect validation to access sensitive internal URLs when wildcard redirect URIs are configured. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 17 Apr 2024 - **Updated:** 4 Aug 2026 - **Also known as:** GHSA-72vp-xfrc-42xm ## What is CVE-2024-1132? CVE-2024-1132 is a high-severity path traversal vulnerability in Redhat Build of Keycloak, published on 17 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description A flaw was found in Keycloak, where it does not properly validate URLs included in a redirect. This issue could allow an attacker to construct a malicious request to bypass validation and access other URLs and sensitive information within the domain or conduct further attacks. This flaw affects any client that utilizes a wildcard in the Valid Redirect URIs field, and requires user interaction within the malicious URL. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2024-1132? 4 open source packages ship an affected version, including org.keycloak:keycloak-services. It affects 10 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.keycloak:keycloak-services` | Maven | All versions | 22.0.10 | | `org.keycloak:keycloak-services` | Maven | All versions | 22.0.10 | | `org.keycloak:keycloak-services` | Maven | From 23.0.0 | 24.0.3 | | `org.keycloak:keycloak-services` | Maven | From 23.0.0 | 24.0.3 | Products: Redhat Build of Keycloak, Redhat Jboss Middleware Text-Only Advisories, Redhat Keycloak, Redhat Migration Toolkit for Applications, Redhat Migration Toolkit for Runtimes, Redhat Openshift Container Platform, Redhat Openshift Container Platform for Ibm Z, Redhat Openshift Container Platform for Linuxone, Redhat Openshift Container Platform for Power, Redhat Single Sign-On. ## How do I fix CVE-2024-1132? Upgrade org.keycloak:keycloak-services to a fixed version for your release line: 22.0.10 or 24.0.3. ## Is CVE-2024-1132 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1132 exists. ## Other vulnerabilities in Redhat Build of Keycloak - [CVE-2026-15572](https://insights.sbomify.com/CVE-2026-15572/): Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation (high 8.8) - [CVE-2026-3047](https://insights.sbomify.com/CVE-2026-3047/): Keycloak SAML Broken has Authentication Bypass by Primary Weakness (high 8.8) - [CVE-2026-15573](https://insights.sbomify.com/CVE-2026-15573/): Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher (high 8.1) - [CVE-2026-16102](https://insights.sbomify.com/CVE-2026-16102/): Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers (high 8.1) - [CVE-2026-1609](https://insights.sbomify.com/CVE-2026-1609/): Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users (high 8.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-1132 and fix it if it is affected. What it is: CVE-2024-1132 is a high-severity path traversal vulnerability in Redhat Build of Keycloak, published on 17 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1132 exists. Affected packages and fixed versions: - org.keycloak:keycloak-services (Maven): affected all versions; fixed in 22.0.10 - org.keycloak:keycloak-services (Maven): affected all versions; fixed in 22.0.10 - org.keycloak:keycloak-services (Maven): affected from 23.0.0; fixed in 24.0.3 - org.keycloak:keycloak-services (Maven): affected from 23.0.0; fixed in 24.0.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-1132/ (Markdown: https://insights.sbomify.com/CVE-2024-1132/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1132 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1132 - OSV: https://osv.dev/vulnerability/CVE-2024-1132 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-1132/ Summaries are generated and may contain mistakes; the official description above is the record.