# CVE-2026-1518: Keycloak Server-Side Request Forgery (SSRF) vulnerability


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Feb 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-fwhw-chw4-gh37

## What is CVE-2026-1518?

CVE-2026-1518 is a vulnerability in org.keycloak:keycloak-parent, published on 2 Feb 2026. 

### Official description

DO NOT USE THIS CANDIDATE NUMBER. After further review by the Keycloak project and Red Hat, the reported SSRF via client registration/backchannel notification URIs was determined not to constitute a security vulnerability. The reported behavior is expected administrator-controlled functionality, and Keycloak provides documented mitigations through Client Policies, including the Secure Client URIs Pattern executor. Therefore, this CVE has been rejected.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-parent` | Maven | All versions to 26.5.2 | None |
| `org.keycloak:keycloak-parent` | Maven | All versions to 26.5.2 | None |

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

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

## Is CVE-2026-1518 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1518 is a vulnerability in org.keycloak:keycloak-parent, published on 2 Feb 2026. 
Exploitation: There is no known exploitation of CVE-2026-1518 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-parent (Maven): affected all versions up to 26.5.2; no fix listed
- org.keycloak:keycloak-parent (Maven): affected all versions up to 26.5.2; 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-1518/ (Markdown: https://insights.sbomify.com/CVE-2026-1518/index.md)
```

## Sources

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

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