Security readout for executives and security teams
Plain-English summary
Docker Model Runner before 1.0.16 lets an unauthenticated caller change runtime flags through a configuration endpoint. In Docker Desktop, default containers can reach this service, so a malicious or compromised container could overwrite important files and potentially destroy Docker Desktop data. Docker says specific conditions and user interaction may allow container escape.
Executive priority
Treat as high priority for developer workstations and AI/model-running environments. The main business risk is local Docker data destruction and, under narrower conditions, container escape. Prioritize updates on machines running untrusted containers or using Docker Desktop Model Runner defaults.
Technical view
The unauthenticated POST /engines/_configure endpoint accepts arbitrary runtime flags and passes them to llama.cpp. Abuse of the --log-file flag can write or overwrite files accessible to the Model Runner process. Docker Desktop enables Model Runner by default since 4.46.0 and exposes it to default containers at model-runner.docker.internal. Fixed in Docker Model Runner 1.0.16 and Docker Desktop 4.61.0.
Likely exposure
Highest exposure is Docker Desktop installations from 4.46.0 through versions before 4.61.0 with Model Runner enabled. Standalone Docker Model Runner versions before 1.0.16 are affected. Risk increases if untrusted containers run locally or if Model Runner is exposed over localhost TCP in specific configurations.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked KEV. Exploitation requires access to the Model Runner API. In Docker Desktop, default containers can reach it without authentication. The source notes destructive overwrite of Docker.raw and possible container escape only in specific configurations with user interaction.
Researcher notes
The advisory describes an unauthenticated configuration surface rather than a memory-corruption issue. CVSS is 7.6 with scope changed and high CIA impact, but attack complexity and user interaction are noted. Evidence for container escape is conditional; do not assume universal host compromise from the provided sources.
Mitigation direction
- Update Docker Model Runner to 1.0.16 or later.
- Update Docker Desktop to 4.61.0 or later.
- Enable Enhanced Container Isolation where available.
- Avoid exposing Docker Model Runner over localhost TCP.
- Review Docker advisory for the named workaround details.
Validation and detection
- Inventory Docker Desktop versions across developer endpoints.
- Identify standalone Docker Model Runner deployments below 1.0.16.
- Check whether Model Runner is enabled on Docker Desktop hosts.
- Confirm Enhanced Container Isolation is enabled where required.
- Review configurations exposing Model Runner to localhost TCP.
- Assess whether untrusted containers run on affected hosts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-749: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-28400 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H0.86Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.6HighVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/docker/model-runner/security/advisories/GHSA-m456-c56c-hh5cCVE reference · x_refsource_CONFIRM
- https://www.zerodayinitiative.com/advisories/ZDI-CAN-28379CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposed Dangerous Method or Function
Exposed Dangerous Method or Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
