High [CVE-2026-5843] Docker Desktop: 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
This high-severity Docker advisory covers CVE-2026-5843; related products: Docker Desktop, Docker Model Runner.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Docker Docker Desktop publishes the next one.
See Docker Docker Desktop's last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
Summary
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.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.
Official advisory · medium-confidence parse· fetched 4 months ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists. Confirm against the vendor advisory.
Official advisory · medium-confidence parse· fetched 4 months ago·verify at source
Mitigation
The source record does not include mitigation steps. That does not mean no fix exists. Read the vendor advisory below for the authoritative guidance.
Official advisory · medium-confidence parse· fetched 4 months ago·verify at source
More Docker advisories
- CVE-2026-5817May 22, 2026Docker Desktop: The vllm-metal inference backend in Docker Model Runner on macOS
- CVE-2026-112917Nov 3, 2026In Docker Desktop for Windows with the WSL2 backend, an unprivileged Linux container can
- CVE-2026-114409Oct 27, 2026Docker Desktop before version 4.97.0 could write third-party API keys and OAuth access
- CVE-2026-106581Oct 9, 2026Before 4.92.0, Docker Desktop for Windows did not verify the signature of a package
- CVE-2026-17106Aug 18, 2026The tar extraction routines in moby/go-archive
- CVE-2026-8936Jun 2, 2026Docker Desktop: Fixed a VM panic caused by unbounded recursion in the grpcfuse kernel
Android app · Google Play
Monitor future Docker CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.