{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-5817 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5817 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5817 is a high-severity code injection vulnerability in Docker Desktop, published on 22 May 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5817 and fix it if it is affected.\n\nWhat it is: CVE-2026-5817 is a high-severity code injection vulnerability in Docker Desktop, published on 22 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-5817 in the wild and no public exploit code.\n\nAffected product: Docker Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-5817/ (Markdown: https://insights.sbomify.com/CVE-2026-5817/index.md)","id":"CVE-2026-5817","markdown":"https://insights.sbomify.com/CVE-2026-5817/index.md","name":"CVE-2026-5817","record":{"aliases":["GHSA-cgqp-ww2v-6rjh"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Docker Model Runner","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code on the Docker host by triggering inference with a malicious model due to unsandboxed trust_remote_code settings.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[{"product":"docker_desktop","vendor":"docker"}],"cvss":{"score":8.8,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"}],"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.\n\nAny container on the Docker network can trigger this by calling the model-runner.docker.internal API to pull a malicious model and request inference.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-05-20","github_poc":2,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-20T11:31:23Z","kind":"github_poc","ref":"https://github.com/davidrxchester/CVE-2026-5817","stars":0,"title":"Docker Container-to-Host Remote Code Execution POC via vllm-metal trust_remote_code=True"},{"date":"2026-05-22T16:30:23Z","kind":"github_poc","ref":"https://github.com/gouldnicholas/CVE-2026-5817-PoC","stars":0,"title":"Docker Model Runner container-to-host RCE / Escape:  A critical vulnerability that allows for container-to-host code execution in the Docker Model Runner MLX / SGLANG / VLLM inference backend."}],"tier":"poc_unverified"},"has_fix":null,"headline":"Docker Model Runner container-to-host code execution via unsandboxed trust_remote_code in Python inference backends","id":"CVE-2026-5817","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"MCU Firmware Update Authentication Bypass on Caliptra Core","id":"CVE-2026-5818"},"packages":[],"prev":{"headline":"Improper Resolution of Path Equivalence in GitLab","id":"CVE-2026-5816"},"products":["Docker Desktop"],"published":"2026-05-22","related":[{"cvss_score":8.8,"headline":"Docker Model Runner container-to-host code execution via MLX-LM model_file importlib loading","id":"CVE-2026-5843","kev_date_added":null,"published":"2026-05-22"},{"cvss_score":8.8,"headline":"Docker Desktop Enhanced Container Isolation bypass via --use-api-socket CLI flag","id":"CVE-2026-6406","kev_date_added":null,"published":"2026-05-22"},{"cvss_score":8.4,"headline":"Missing authorization in n/a","id":"CVE-2021-44719","kev_date_added":null,"published":"2022-05-25"},{"cvss_score":8,"headline":"Docker Desktop before 4.12.0 is vulnerable to RCE via a crafted extension description or changelog","id":"CVE-2023-0625","kev_date_added":null,"published":"2023-09-25"},{"cvss_score":8,"headline":"Docker Desktop before 4.12.0 is vulnerable to RCE via query parameters in message-box route","id":"CVE-2023-0626","kev_date_added":null,"published":"2023-09-25"},{"cvss_score":8,"headline":"Docker Desktop before 4.23.0 allows Access Token theft via a crafted extension icon URL","id":"CVE-2023-5166","kev_date_added":null,"published":"2023-09-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-27","vendors":["Docker"]},"summary":"Attackers can execute arbitrary code on the Docker host by triggering inference with a malicious model due to unsandboxed trust_remote_code settings.","url":"https://insights.sbomify.com/CVE-2026-5817/"}