# CVE-2026-1180: Keycloak’s OpenID Connect Dynamic Client Registration feature affected by Server-Side Request Forgery (SSRF)

> Attackers can force Keycloak to make arbitrary HTTP requests via jwks_uri, enabling internal network probing and cloud metadata access.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-7vw6-5q2f-7w5r

## What is CVE-2026-1180?

CVE-2026-1180 is a medium-severity server-side request forgery vulnerability in Red Hat Build of Keycloak, published on 20 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was identified in Keycloak’s OpenID Connect Dynamic Client Registration feature when clients authenticate using private_key_jwt. The issue allows a client to specify an arbitrary jwks_uri, which Keycloak then retrieves without validating the destination. This enables attackers to coerce the Keycloak server into making HTTP requests to internal or restricted network resources. As a result, attackers can probe internal services and cloud metadata endpoints, creating an information disclosure and reconnaissance risk.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-1180?

2 open source packages ship an affected version, including org.keycloak:keycloak-adapter-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-adapter-core` | Maven | All versions to 25.0.3 | None |
| `org.keycloak:keycloak-adapter-core` | Maven | All versions to 25.0.3 | None |

## How do I fix CVE-2026-1180?

No fix has been published for CVE-2026-1180 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1180 being exploited?

There is no known exploitation of CVE-2026-1180 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1180 and fix it if it is affected.

What it is: CVE-2026-1180 is a medium-severity server-side request forgery vulnerability in Red Hat Build of Keycloak, published on 20 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1180 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-adapter-core (Maven): affected all versions up to 25.0.3; no fix listed
- org.keycloak:keycloak-adapter-core (Maven): affected all versions up to 25.0.3; no fix listed

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-1180/ (Markdown: https://insights.sbomify.com/CVE-2026-1180/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1180
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1180
- OSV: https://osv.dev/vulnerability/CVE-2026-1180

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1180/
Summaries are generated and may contain mistakes; the official description above is the record.