# CVE-2026-110220: Kubeflow Model Registry through 0.3.17 SSRF via InferenceService Controller URL Annotation

> Namespace users can steal controller ServiceAccount tokens via SSRF in Kubeflow Model Registry, enabling cluster-wide modification of other tenants' InferenceServices.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-q9m2-3393-574q

## What is CVE-2026-110220?

CVE-2026-110220 is a high-severity server-side request forgery vulnerability in Kubeflow Model Registry, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kubeflow Model Registry through 0.3.17 contains a server-side request forgery vulnerability that allows namespace users to steal the controller ServiceAccount token via the modelregistry.kubeflow.org/url annotation. Attackers can create an InferenceService pointing the annotation at their server, capture the bearer token, and modify other tenants' InferenceServices cluster-wide.

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

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


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

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

## Is CVE-2026-110220 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110220 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110220 is a high-severity server-side request forgery vulnerability in Kubeflow Model Registry, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110220 exists.

Affected product: Kubeflow Model Registry. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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