CVE-2026-5843 PUBLISHED

Docker Model Runner container-to-host code execution via MLX-LM model_file importlib loading

Assigner: Docker
Reserved: 08.04.2026 Published: 22.05.2026 Updated: 22.05.2026

The MLX inference backend in Docker Model Runner on macOS uses the MLX-LM library, which unconditionally imports and executes arbitrary Python files from model directories via the model_file configuration field in config.json. When a model's config.json specifies a model_file pointing to a Python file, MLX-LM uses importlib to load and execute it with no trust_remote_code gate or equivalent safety check. The MLX backend runs without sandboxing, resulting in arbitrary code execution on the Docker host as the Docker Desktop user.

Any container on the Docker network can trigger this by calling the model-runner.docker.internal API to pull a malicious model from an attacker-controlled OCI registry and request inference.

Metrics

CVSS Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CVSS Score: 8.8

Product Status

Vendor Docker
Product Docker Desktop
Versions Default: unaffected
  • affected from 4.56.0 to 4.71.0 (excl.)

Affected Configurations

Docker Model Runner enabled with the MLX inference backend on macOS

Workarounds

Disable Docker Model Runner or only run trusted containers on Docker Desktop instances where Model Runner is enabled.

Credits

  • David Rochester (@davidrxchester) finder
  • Nicholas Gould (@gouldnicholas) finder

References

Problem Types

  • CWE-829: Inclusion of Functionality from Untrusted Control Sphere CWE

Impacts

  • CAPEC-480 Escaping Virtualization