# CVE-2024-7260: Keycloak-core: open redirect on account page > Attackers can craft URLs that redirect Keycloak users to malicious sites, facilitating phishing attacks and bypassing domain security checks. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 9 Sep 2024 - **Updated:** 23 Jan 2026 - **Also known as:** BIT-keycloak-2024-7260, GHSA-g4gc-rh26-m3p5 ## What is CVE-2024-7260? CVE-2024-7260 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 9 Sep 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 An open redirect vulnerability was found in Keycloak. A specially crafted URL can be constructed where the referrer and referrer_uri parameters are made to trick a user to visit a malicious webpage. A trusted URL can trick users and automation into believing that the URL is safe, when, in fact, it redirects to a malicious server. This issue can result in a victim inadvertently trusting the destination of the redirect, potentially leading to a successful phishing attack or other types of attacks. Once a crafted URL is made, it can be sent to a Keycloak admin via email for example. This will trigger this vulnerability when the user visits the page and clicks the link. A malicious actor can use this to target users they know are Keycloak admins for further attacks. It may also be possible to bypass other domain-related security checks, such as supplying this as a OAuth redirect uri. The malicious actor can further obfuscate the redirect_uri using URL encoding, to hide the text of the actual malicious website domain. Weakness: CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2024-7260? 3 open source packages ship an affected version, including org.keycloak:keycloak-core and keycloak. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.keycloak:keycloak-core` | Maven | All versions | 24.0.7 | | `org.keycloak:keycloak-core` | Maven | All versions | 24.0.7 | | `keycloak` | Bitnami | All versions | 24.0.7 | Products: Redhat Build of Keycloak, Redhat Keycloak. ## How do I fix CVE-2024-7260? Upgrade org.keycloak:keycloak-core to 24.0.7 or later. ## Is CVE-2024-7260 being exploited? There is no known exploitation of CVE-2024-7260 in the wild and no public exploit code. ## 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-7260 and fix it if it is affected. What it is: CVE-2024-7260 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 9 Sep 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: There is no known exploitation of CVE-2024-7260 in the wild and no public exploit code. Affected packages and fixed versions: - org.keycloak:keycloak-core (Maven): affected all versions; fixed in 24.0.7 - org.keycloak:keycloak-core (Maven): affected all versions; fixed in 24.0.7 - keycloak (Bitnami): affected all versions; fixed in 24.0.7 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-7260/ (Markdown: https://insights.sbomify.com/CVE-2024-7260/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-7260 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-7260 - OSV: https://osv.dev/vulnerability/CVE-2024-7260 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-7260/ Summaries are generated and may contain mistakes; the official description above is the record.