critical CVSS 9.1

CVE-2026-33990·Docker vulnerability

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.

Severity
critical
Software
Docker
Fixed in
1.1.25
Published
2026-04-01

Affected versions

Until: 1.1.25

Fixed in: 1.1.25

How to fix this CVE

Upgrade Docker Model Runner to version 1.1.25 or later immediately, as earlier versions allow attackers to exploit an SSRF vulnerability in the OCI registry token exchange mechanism to access internal services. For Docker Desktop users, enabling Enhanced Container Isolation (ECI) provides an additional layer of protection by restricting container access to the Model Runner component. Verify that Model Runner is not unnecessarily exposed over TCP to untrusted networks after patching.

sudo dnf update docker-ce

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /v2/<registry-path>/token HTTP/1.1|GET /token\?service=|Authorization: Bearer.*internal.*|HTTP/1.1 307.*realm=.*127\.0\.0\.1|realm=.*localhost.*:.*[0-9]{4}

How to check if you are affected

  1. Run `docker --version` and `docker info` to confirm Docker is installed and check the version; versions prior to 1.1.25 are vulnerable
  2. Execute `docker ps --all` and inspect running containers for those using model-runner; cross-reference with `docker inspect <container-id>` to identify exposed ports or network bridges
  3. Search Docker daemon logs for failed token exchange requests: `sudo journalctl -u docker -n 500 | grep -i 'realm\|token\|registry'` and look for unexpected redirects to 127.0.0.1 or internal IP addresses
  4. Confirm the patch by running `docker --version` again after the upgrade and verify the version is >= 1.1.25

FAQ

What is CVE-2026-33990?

CVE-2026-33990 is a Server-Side Request Forgery (SSRF) vulnerability in Docker Model Runner that allows an attacker-controlled OCI registry to redirect token exchange requests to arbitrary internal services, potentially exposing sensitive data and service responses.

Is CVE-2026-33990 being actively exploited?

According to CISA, CVE-2026-33990 is not currently listed in the Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available. However, the attack requires minimal complexity and should be treated as high-priority due to its critical severity.

What versions of Docker are affected by CVE-2026-33990?

All versions of Docker Model Runner prior to 1.1.25 are affected. Users running version 1.1.25 or later are protected against this vulnerability.

How do I check if my server is vulnerable to CVE-2026-33990?

Run `docker --version` to determine your installed Docker version. If the version is below 1.1.25, your system is vulnerable. Additionally, check for exposed Model Runner TCP ports using `sudo netstat -tlnp | grep -i docker` or `sudo ss -tlnp | grep -i docker`.

Does Defensia detect CVE-2026-33990?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server, CVE-2026-33990 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-33587CVSS 10Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and subsequently OS commands) on the docker container via Server-Side Template Injection (SSTI) for user-created transformations.
CVE-2026-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
CVE-2026-53576CVSS 10Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.
CVE-2026-42298CVSS 10Postiz is an AI social media scheduling tool. Prior to commit da44801, a "Pwn Request" vulnerability in the Build and Publish PR Docker Image workflow (.github/workflows/pr-docker-build.yml) allows any unauthenticated user to execute arbitrary code during the Docker build process and exfiltrate a highly privileged GITHUB_TOKEN (write-all permissions). This can be achieved simply by opening a Pull Request from a fork with a maliciously modified Dockerfile.dev. This issue has been patched via commit da44801.
CVE-2026-40281CVSS 10Gotenberg is a Docker-powered stateless API for PDF files. In versions 8.30.1 and earlier, the metadata write endpoint validates metadata keys for control characters but leaves metadata values unsanitized. A newline character in a metadata value splits the ExifTool stdin line into two separate arguments, allowing injection of arbitrary ExifTool pseudo-tags such as -FileName, -Directory, -SymLink, and -HardLink. This is a bypass of the incomplete key-sanitization fix introduced in v8.30.1. An unauthenticated attacker can rename or move any PDF being processed to an arbitrary path in the container filesystem, overwrite arbitrary files, or create symlinks and hard links at arbitrary paths.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-33990. Free for 1 server.

Get started free