# CVE-2026-33990: Docker Model Runner OCI Registry Client Vulnerable to Server-Side Request Forgery (SSRF)

> A malicious OCI registry can trigger Server-Side Request Forgery in Docker Model Runner, allowing attackers to access internal services and exfiltrate data.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Apr 2026
- **Updated:** 4 Apr 2026
- **Also known as:** GHSA-x2f5-332j-9xwq, GO-2026-4911, UBUNTU-CVE-2026-33990

## What is CVE-2026-33990?

CVE-2026-33990 is a medium-severity server-side request forgery vulnerability in docker model-runner, published on 1 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Docker Model Runner (DMR) is software used to manage, run, and deploy AI models using Docker. Prior to version 1.1.25, Docker Model Runner contains an SSRF vulnerability in its OCI registry token exchange flow. When pulling a model, Model Runner follows the realm URL from the registry's WWW-Authenticate header without validating the scheme, hostname, or IP range. A malicious OCI registry can set the realm to an internal URL (e.g., http://127.0.0.1:3000/), causing Model Runner running on the host to make arbitrary GET requests to internal services and reflect the full response body back to the caller. Additionally, the token exchange mechanism can relay data from internal services back to the attacker-controlled registry via the Authorization: Bearer header. This issue has been patched in version 1.1.25. For Docker Desktop users, enabling Enhanced Container Isolation (ECI) blocks container access to Model Runner, preventing exploitation. However, if the Docker Model Runner is exposed to localhost over TCP in specific configurations, the vulnerability is still exploitable.

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

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

3 open source packages ship an affected version, including github.com/docker/model-runner. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/docker/model-runner` | Go | All versions | 1.1.25 |
| `github.com/docker/model-runner` | Go | All versions | 1.1.25 |
| `github.com/docker/model-runner` | Go | All versions | 1.1.25 |

Products: Docker Model Runner.

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

Upgrade github.com/docker/model-runner to 1.1.25 or later.

## Is CVE-2026-33990 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33990 is a medium-severity server-side request forgery vulnerability in docker model-runner, published on 1 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33990 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/docker/model-runner (Go): affected all versions; fixed in 1.1.25
- github.com/docker/model-runner (Go): affected all versions; fixed in 1.1.25
- github.com/docker/model-runner (Go): affected all versions; fixed in 1.1.25

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

## Sources

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

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