Quick answers
- Is CVE-2026-5817 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-5817 being exploited in the wild.
- How severe is CVE-2026-5817?
- High severity, with a CVSS score of 8.2, published 22 May 2026.
- Which products and versions are affected?
- Docker Docker Desktop 4.62.0 to 4.68.0.
- Is there a fix for CVE-2026-5817?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-5817 attacked?
- It is attacked with local access or over the network, in a network appliance.
- Am I affected by CVE-2026-5817?
- Check whether you run Apple macOS or Docker Desktop. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vllm-metal inference backend in Docker Model Runner (DMR) on macOS unconditionally sets 'trust_remote_code=True' when calling 'transformers.AutoTokenizer.from_pretrained()'. Because the backend runs without sandboxing, it imports and executes arbitrary Python files included in any model pulled from an OCI registry. An attacker can trigger this by sending a request to the 'model-runner.docker.internal' API from any container on the Docker network to pull a malicious model and initiate inference. This results in arbitrary code execution on the Docker host as the Docker Desktop user. The issue is addressed in Docker Desktop version 4.68.0.
Affected products
- Docker Docker Desktop 4.62.0 to 4.68.0
Timeline
- 2026-05-22: disclosed
- 2026-05-22: advisory
- 2026-06-01: other: NIST analysis completed