Nitesh Surana’s new technical account explains how Docker Model Runner let a default container influence a process running on its host. The flaw, CVE-2026-28400, could overwrite files accessible to that process. On macOS, that included Docker Desktop’s virtual-machine disk and its stored containers, images and volumes.

This is fresh research about an already-patched vulnerability. Docker’s official advisory lists Model Runner versions before 1.0.16 as affected and 1.0.16 as repaired. Docker Desktop users received that repair in 4.61.0 or later. The practical response is to verify the installed repair and review which containers can reach host-side model services.

Local inference crossed the container boundary

Docker Model Runner serves models through an API compatible with OpenAI clients. In the researched Docker Desktop configurations on macOS and Windows, the inference process runs on the host, with the Docker Desktop user’s privileges. The Linux containers run inside a virtual machine.

The vulnerable API accepted runtime options without authentication and passed them to the model server. A container created with ordinary privileges could reach that service. File-operation options consequently operated with the host process’s permitted access, rather than the container’s filesystem view.

The platform restrictions differed. Surana describes a macOS sandbox that allowed writes within Docker’s data directory. On Windows, the process-management restrictions used by Docker did not provide equivalent filesystem isolation. Available access still depended on the user’s operating-system permissions.

Docker says Model Runner has been enabled by default in Docker Desktop since 4.46.0. The research excludes Docker Desktop for Linux and Windows-container mode. Its findings should not be generalized to every Docker Engine installation or local model server.

File destruction and code execution had different conditions

Evidence status: controlled research demonstrations and a vendor-confirmed vulnerability. Neither reviewed source reports an identified in-the-wild campaign exploiting this flaw.

The base file-overwrite problem could destroy Docker Desktop’s data disk. Surana’s fuller container-to-host code-execution chain also required:

  • A Docker Extension already installed.
  • A malicious image being run, or an existing container being compromised.
  • The user subsequently opening the extension’s interface.

An extension is an add-on to Docker Desktop with access to host operations. The demonstrated chain altered extension assets and relied on that interface being opened. Those conditions belong beside the code-execution claim; a normal container alone does not establish that the complete chain has run.

The report also describes ZDI-26-451, a separate macOS sandbox escape that first requires code execution inside the inference sandbox. Its July advisory links Docker’s repair commit without naming a fixed Desktop release. The 4.61.0 repair target above is specifically verified for CVE-2026-28400, not a blanket version claim for every chain in the article.

A separate Windows extension pivot assumes prior access inside the Docker Desktop virtual machine or equivalent powerful access. Docker told the researcher that scenario fell outside its threat model. It is not another independently demonstrated default-container entry point.

Check the repair and reduce access to host services

Docker’s advisory supports these immediate steps:

  • Update Docker Desktop to 4.61.0 or later, or standalone Model Runner to 1.0.16 or later. These are the minimum fixes named for this vulnerability, not recommendations to stop updating there.
  • Verify which Model Runner version is actually deployed. A wrapper application or familiar container command does not prove that inference stays inside a container.
  • Where available, Enhanced Container Isolation blocks the ordinary container route to Model Runner. Docker warns that specific configurations exposing Model Runner over localhost TCP can still leave an exploitable path. Treat this as a qualified workaround, not a substitute for the update.
  • Review unneeded extension and host-service access. Extensions, shared host files and local management APIs create separate trust relationships. Container privilege flags alone do not describe those relationships.
  • Keep important recovery copies outside Docker Desktop’s virtual disk. A backup stored only in a volume on the same disk shares the failure described here.

A system suspected of prior host-file modification needs investigation as well as a patch. The sources provide no universal credential-theft count or basis for declaring every older installation compromised.

Surana’s article was published November 18, according to both its displayed date and structured metadata, despite November 17 appearing in its URL. Its later explanation does not change the older vulnerability’s disclosure or patch timeline.

Caveat: TrendAI, a security vendor, supplies the research; the demonstrated host-code chain depends on extension installation and later user interaction.