# CVE-2026-4874: Keycloak Server-Side Request Forgery via OIDC token endpoint manipulation > Authenticated attackers can perform SSRF via token endpoint manipulation in Keycloak when specific logout configurations are enabled, allowing internal network probing. - **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Mar 2026 - **Updated:** 26 Jun 2026 - **Also known as:** ECHO-1b74-757a-0a67, GHSA-22rm-wp4x-v5cx, MINI-fjg7-pcfc-jg7h, MINI-v6pv-3f3f-2qv5 ## What is CVE-2026-4874? CVE-2026-4874 is a low-severity server-side request forgery vulnerability in Redhat Build of Keycloak, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A flaw was found in Keycloak. An authenticated attacker can perform Server-Side Request Forgery (SSRF) by manipulating the `client_session_host` parameter during refresh token requests. This occurs when a Keycloak client is configured to use the `backchannel.logout.url` with the `application.session.host` placeholder. Successful exploitation allows the attacker to make HTTP requests from the Keycloak server’s network context, potentially probing internal networks or internal APIs, leading to information disclosure. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2026-4874? 4 open source packages ship an affected version, including org.keycloak:keycloak-services. It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.keycloak:keycloak-services` | Maven | All versions | 26.4.13 | | `org.keycloak:keycloak-services` | Maven | All versions | 26.4.13 | | `org.keycloak:keycloak-services` | Maven | From 26.5.0 | 26.6.3 | | `org.keycloak:keycloak-services` | Maven | From 26.5.0 | 26.6.3 | Products: Redhat Build of Keycloak, Redhat Jboss Enterprise Application Platform, Redhat Jboss Enterprise Application Platform Expansion Pack, Redhat Single Sign-On. ## How do I fix CVE-2026-4874? Upgrade org.keycloak:keycloak-services to a fixed version for your release line: 26.4.13 or 26.6.3. ## Is CVE-2026-4874 being exploited? There is no known exploitation of CVE-2026-4874 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-2026-4874 and fix it if it is affected. What it is: CVE-2026-4874 is a low-severity server-side request forgery vulnerability in Redhat Build of Keycloak, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-4874 in the wild and no public exploit code. Affected packages and fixed versions: - org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.4.13 - org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.4.13 - org.keycloak:keycloak-services (Maven): affected from 26.5.0; fixed in 26.6.3 - org.keycloak:keycloak-services (Maven): affected from 26.5.0; fixed in 26.6.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-2026-4874/ (Markdown: https://insights.sbomify.com/CVE-2026-4874/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4874 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4874 - OSV: https://osv.dev/vulnerability/CVE-2026-4874 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-4874/ Summaries are generated and may contain mistakes; the official description above is the record.