Docker Desktop up to 4.70.x MLX Inference Backend config.json model_file inclusion of functionality from untrusted control sphere
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Docker Desktop up to 4.70.x. Affected is an unknown function of the file config.json of the component MLX Inference Backend. Such manipulation of the argument model_file leads to inclusion of functionality from untrusted control sphere. This vulnerability is documented as CVE-2026-5843. The attack needs to be performed locally. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Docker Desktop up to 4.70.x. Affected by this issue is some unknown functionality of the file config.json of the component MLX Inference Backend. The manipulation of the argument model_file with an unknown input leads to a inclusion of functionality from untrusted control sphere vulnerability. Using CWE to declare the problem leads to CWE-829. The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was released by David Rochester. The advisory is shared for download at docs.docker.com. This vulnerability is handled as CVE-2026-5843 since 04/08/2026. The exploitation is known to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available.
By approaching the search of inurl:config.json it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 316463 (Docker Desktop < 4.71.0 Container Escape (CVE-2026-5843)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.71.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (316463). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
- 4.0
- 4.1
- 4.2
- 4.3
- 4.4
- 4.5
- 4.6
- 4.7
- 4.8
- 4.9
- 4.10
- 4.11
- 4.12
- 4.13
- 4.14
- 4.15
- 4.16
- 4.17
- 4.18
- 4.19
- 4.20
- 4.21
- 4.22
- 4.23
- 4.24
- 4.25
- 4.26
- 4.27
- 4.28
- 4.29
- 4.30
- 4.31
- 4.32
- 4.33
- 4.34
- 4.35
- 4.36
- 4.37
- 4.38
- 4.39
- 4.40
- 4.41
- 4.42
- 4.43
- 4.44
- 4.45
- 4.46
- 4.47
- 4.48
- 4.49
- 4.50
- 4.51
- 4.52
- 4.53
- 4.54
- 4.55
- 4.56
- 4.57
- 4.58
- 4.59
- 4.60
- 4.61
- 4.62
- 4.63
- 4.64
- 4.65
- 4.66
- 4.67
- 4.68
- 4.69
- 4.70
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.8
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.2
CNA Vector (Docker): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Inclusion of functionality from untrusted control sphereCWE: CWE-829
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 316463
Nessus Name: Docker Desktop < 4.71.0 Container Escape (CVE-2026-5843)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Desktop 4.71.0
Timeline
04/08/2026 CVE reserved05/23/2026 Advisory disclosed
05/23/2026 VulDB entry created
05/23/2026 VulDB entry last update
Sources
Advisory: docs.docker.comResearcher: David Rochester
Status: Confirmed
CVE: CVE-2026-5843 (🔒)
GCVE (CVE): GCVE-0-2026-5843
GCVE (VulDB): GCVE-100-365276
Entry
Created: 05/23/2026 07:49Updated: 05/23/2026 18:20
Changes: 05/23/2026 07:49 (79), 05/23/2026 18:20 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.