# CVE-2026-28400: Docker Model Runner Unauthenticated Runtime Flag Injection via _configure Endpoint

> Unauthenticated attackers can inject runtime flags to overwrite files, potentially destroying Docker data or escaping containers.

- **Severity:** High 7.6 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Feb 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-m456-c56c-hh5c

## What is CVE-2026-28400?

CVE-2026-28400 is a high-severity command injection vulnerability in docker model-runner, published on 27 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Docker Model Runner (DMR) is software used to manage, run, and deploy AI models using Docker. Versions prior to 1.0.16 expose a  POST `/engines/_configure`  endpoint that accepts arbitrary runtime flags without authentication. These flags are passed directly to the underlying inference server (llama.cpp). By injecting the  --log-file  flag, an attacker with network access to the Model Runner API can write or overwrite arbitrary files accessible to the Model Runner process. When bundled with Docker Desktop (where Model Runner is enabled by default since version 4.46.0), it is reachable from any default container at  model-runner.docker.internal  without authentication. In this context, the file overwrite can target the Docker Desktop VM disk (`Docker.raw` ), resulting in the destruction of all containers, images, volumes, and build history. However, in specific configurations and with user interaction, it is possible to convert this vulnerability in a container escape. The issue is fixed in Docker Model Runner 1.0.16. Docker Desktop users should update to 4.61.0 or later, which includes the fixed Model Runner. A workaround is available. 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-749 (Exposed Dangerous Method or Function)

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


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

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

## Is CVE-2026-28400 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28400 is a high-severity command injection vulnerability in docker model-runner, published on 27 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-28400 in the wild and no public exploit code.

Affected product: docker model-runner. 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-28400/ (Markdown: https://insights.sbomify.com/CVE-2026-28400/index.md)
```

## Sources

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

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