CVE-2026-5817: CWE-829: Inclusion of Functionality from Untrusted Control Sphere in Docker Docker Desktop
The vllm-metal inference backend in Docker Model Runner on macOS unconditionally sets trust_remote_code=True when loading model tokenizers, and runs without sandboxing. This causes transformers.AutoTokenizer.from_pretrained() to import and execute arbitrary Python files included in any model pulled from an OCI registry, resulting in arbitrary code execution on the Docker host as the Docker Desktop user when inference is triggered. Any container on the Docker network can trigger this by calling the model-runner.docker.internal API to pull a malicious model and request inference.
AI Analysis
Technical Summary
The vulnerability CVE-2026-5817 affects Docker Desktop 4.62.0 on macOS through the vllm-metal inference backend in Docker Model Runner. It unconditionally enables trust_remote_code when loading model tokenizers, allowing transformers.AutoTokenizer.from_pretrained() to execute arbitrary Python files included in any model pulled from an OCI registry. This leads to arbitrary code execution on the host as the Docker Desktop user. Exploitation can be triggered by any container on the Docker network via the model-runner.docker.internal API by pulling a malicious model and requesting inference. The vulnerability is classified under CWE-829 (Inclusion of Functionality from Untrusted Control Sphere). No patch or official remediation has been published yet.
Potential Impact
Successful exploitation results in arbitrary code execution on the Docker host with the privileges of the Docker Desktop user. This can be triggered remotely by any container on the Docker network, potentially compromising the host system and any data or processes accessible to the Docker Desktop user. The vulnerability thus poses a significant risk to host integrity and confidentiality.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider restricting network access to the model-runner.docker.internal API and avoid running untrusted containers or pulling untrusted models that could trigger inference. Monitoring vendor communications for updates is recommended.
CVE-2026-5817: CWE-829: Inclusion of Functionality from Untrusted Control Sphere in Docker Docker Desktop
Description
The vllm-metal inference backend in Docker Model Runner on macOS unconditionally sets trust_remote_code=True when loading model tokenizers, and runs without sandboxing. This causes transformers.AutoTokenizer.from_pretrained() to import and execute arbitrary Python files included in any model pulled from an OCI registry, resulting in arbitrary code execution on the Docker host as the Docker Desktop user when inference is triggered. Any container on the Docker network can trigger this by calling the model-runner.docker.internal API to pull a malicious model and request inference.
CVSS v4.0
Score 8.8high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-5817 affects Docker Desktop 4.62.0 on macOS through the vllm-metal inference backend in Docker Model Runner. It unconditionally enables trust_remote_code when loading model tokenizers, allowing transformers.AutoTokenizer.from_pretrained() to execute arbitrary Python files included in any model pulled from an OCI registry. This leads to arbitrary code execution on the host as the Docker Desktop user. Exploitation can be triggered by any container on the Docker network via the model-runner.docker.internal API by pulling a malicious model and requesting inference. The vulnerability is classified under CWE-829 (Inclusion of Functionality from Untrusted Control Sphere). No patch or official remediation has been published yet.
Potential Impact
Successful exploitation results in arbitrary code execution on the Docker host with the privileges of the Docker Desktop user. This can be triggered remotely by any container on the Docker network, potentially compromising the host system and any data or processes accessible to the Docker Desktop user. The vulnerability thus poses a significant risk to host integrity and confidentiality.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider restricting network access to the model-runner.docker.internal API and avoid running untrusted containers or pulling untrusted models that could trigger inference. Monitoring vendor communications for updates is recommended.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Docker
- Date Reserved
- 2026-04-08T15:34:05.200Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a10b5b4e1370fbb4848af58
Added to database: 05/22/2026, 19:59:48 UTC
Last enriched: 05/29/2026, 20:27:05 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 109
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.