Model RunnerApplication · Docker
CVE-2026-33990
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDocker 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDocker Model Runner (DMR) versions prior to 1.1.25 contain an SSRF vulnerability in the OCI registry token exchange flow. The application follows the realm URL from the registry's WWW-Authenticate header without validating the scheme, hostname, or IP range, allowing a malicious registry to redirect DMR to internal services (e.g., http://127.0.0.1:3000/). The token exchange mechanism additionally relays internal service responses back to the attacker via the Authorization: Bearer header, enabling data exfiltration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Model RunnerApplication
< 1.1.25CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Docker Model Runner installation and versionRun 'dmr --version' or check Docker Desktop's installed components for Docker Model Runner. Alternatively, check the Docker Desktop version which includes DMR.Affected if The installed version is below 1.1.25
-
Verify if OCI registry pull functionality is enabledCheck DMR configuration for registry credentials or recent image pull operations. Look for config files in ~/.docker/dmr/ or similar configuration directories.Affected if DMR is configured to authenticate with OCI registries, as the vulnerability triggers during token exchange flow
-
Inspect DMR logs for registry authentication attemptsReview DMR logs (available via Docker Desktop logs or 'docker logs dmr-container' if running as container) for WWW-Authenticate header processing and token exchange requests.Affected if Logs show registry token exchanges with unusual or internal URLs in the realm parameter
-
Monitor for unexpected outbound connections from DMRUse network monitoring (netstat, Wireshark, or host firewall logs) to observe connections initiated by DMR process to internal IP ranges (127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16).Affected if DMR is making outbound connections to internal/private network addresses when interacting with registries
-
Check for exposed localhost services being accessedReview application logs of services running on localhost (ports 3000, 8080, etc.) for requests originating from DMR's user agent or process.Affected if Internal services show requests from DMR that were not initiated by legitimate local operations
You are affected if Docker Model Runner version is below 1.1.25 AND the application is being used to pull images from OCI registries, enabling the vulnerable token exchange flow.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.1.25
Upgrade Docker Model Runner to version 1.1.25 or later. For Docker Desktop users, enabling Enhanced Container Isolation (ECI) provides additional protection, though ECI does not fully mitigate if DMR is exposed to localhost over TCP in certain configurations.
1.1.25
- Upgrade Docker Model Runner to version 1.1.25 or later. Consult the Docker Model Runner release notes or upgrade documentation for your installation method (e.g., Docker Desktop, standalone binary, etc.) to obtain the updated version.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Model Runner
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33990 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data