CVE-2026-28400: Docker Desktop for Mac Docker Model Runner Exposed Dangerous Function Denial-of-Service Vulnerability

Published Feb 27, 2026
·
Updated

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.

Other sources

This vulnerability allows local attackers to create a denial-of-service condition on affected installations of Docker Desktop. An attacker must first obtain the ability to execute low-privileged code on the target guest system in order to exploit this vulnerability. The specific flaw exists within Docker Model Runner. The issue results from the exposure of a dangerous function. An attacker can leverage this vulnerability to create a denial-of-service condition on the system.

ZDI

Affected Software

2 affected components
Docker Docker Model Runner<1.0.16
Docker Docker Desktop<4.61.0

Event History

Feb 27, 2026
CVE Published
via MITRE·09:06 PM
Data Sourced
via MITRE·09:06 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness
Mar 9, 2026
Advisory Published
via ZDI·09:29 PM
Data Sourced
via ZDI·09:29 PM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-28400?

CVE-2026-28400 is considered a high-severity vulnerability due to its potential for unauthenticated runtime flag injection.

2

How do I fix CVE-2026-28400?

To mitigate CVE-2026-28400, upgrade Docker Model Runner to version 1.0.16 or later immediately.

3

What versions of Docker Model Runner are affected by CVE-2026-28400?

CVE-2026-28400 affects all Docker Model Runner versions prior to 1.0.16.

4

Can CVE-2026-28400 be exploited remotely?

Yes, CVE-2026-28400 can be exploited remotely due to the unauthenticated access to the vulnerable endpoint.

5

What does CVE-2026-28400 allow attackers to do?

CVE-2026-28400 allows attackers to inject arbitrary runtime flags into the Docker Model Runner without authentication.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203