What is CVE-2026-33990?

CVE-2026-33990 is a medium-severity server-side request forgery (SSRF) vulnerability in github.com/docker/model-runner (go), affecting versions < 1.1.25. It is fixed in 1.1.25. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

Which versions of github.com/docker/model-runner are affected by CVE-2026-33990?

github.com/docker/model-runner (go) versions < 1.1.25 is affected.

Is there a fix for CVE-2026-33990?

Yes. CVE-2026-33990 is fixed in 1.1.25. Upgrade to this version or later.

Is CVE-2026-33990 exploitable, and should I be worried?

Whether CVE-2026-33990 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-33990 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-33990?

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

CVE-2026-33990 in github.com/docker/model-runner

Q: Which versions of github.com/docker/model-runner are affected by CVE-2026-33990?

github.com/docker/model-runner (go) versions < 1.1.25 is affected.

Q: Is there a fix for CVE-2026-33990?

Yes. CVE-2026-33990 is fixed in 1.1.25. Upgrade to this version or later.

Q: Is CVE-2026-33990 exploitable, and should I be worried?

Whether CVE-2026-33990 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-33990 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-33990?

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

Summary

Docker Model Runner OCI Registry Client Vulnerable to Server-Side Request Forgery (SSRF)

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.

Workarounds

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.

Impact

An unprivileged container or a malicious OCI registry that the user performed a pull from might issue GET requests to host-local services (localhost, internal network)

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Affected versions

github.com/docker/model-runner (< 1.1.25)

Security releases

github.com/docker/model-runner → 1.1.25 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Fixed in Docker Model Runner v1.1.25
Docker Desktop users should update to 4.67.0 or later, which includes the fixed Model Runner.

Frequently Asked Questions

What is CVE-2026-33990? CVE-2026-33990 is a medium-severity server-side request forgery (SSRF) vulnerability in github.com/docker/model-runner (go), affecting versions < 1.1.25. It is fixed in 1.1.25. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
Which versions of github.com/docker/model-runner are affected by CVE-2026-33990? github.com/docker/model-runner (go) versions < 1.1.25 is affected.
Is there a fix for CVE-2026-33990? Yes. CVE-2026-33990 is fixed in 1.1.25. Upgrade to this version or later.
Is CVE-2026-33990 exploitable, and should I be worried? Whether CVE-2026-33990 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-33990 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-33990? Upgrade github.com/docker/model-runner to 1.1.25 or later.