dbcve.org
Docker DesktopApplication · Docker

CVE-2026-5817

HIGH · 8.6 CVSS v3.1 Published 2026-05-22
Fix available
A fix is available. Upgrade to 4.68.0 or later.
See remediation →
89/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vllm-metal inference backend in Docker Model Runner on macOS unconditionally sets trust_remote_code=True when loading tokenizers via transformers.AutoTokenizer.from_pretrained(), causing arbitrary Python files in pulled models to be imported and executed. Combined with the lack of sandboxing, any container on the Docker network can achieve arbitrary code execution on the Docker host by pulling a malicious model and triggering inference.

MitigationDisable trust_remote_code=True by default or implement strict validation before enabling it, and run the inference backend within a properly isolated sandbox to prevent host compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Docker DesktopApplication
Affected:>= 4.62.0, < 4.68.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Docker Desktop version
    Run 'docker --version' or check the Docker Desktop UI to identify the installed version number
    Affected if The version is greater than or equal to 4.62.0 and less than 4.68.0
  2. Verify Docker Model Runner is in use
    Check if Docker Model Runner is installed or enabled on the macOS host. Look for docker-model-runner processes or check installed components in Docker Desktop settings
    Affected if Docker Model Runner is actively being used for model inference workloads
  3. Confirm vllm-metal backend is configured
    Inspect the Docker Model Runner configuration to determine if the vllm-metal inference backend is specified or enabled for model loading
    Affected if The vllm-metal backend is configured and used for inference
  4. Check model source configuration
    Review model loading configuration to determine if models are being pulled from remote OCI registries or Hugging Face-style model hubs
    Affected if Models are loaded from remote or untrusted model registries rather than exclusively local sources

You are affected if running Docker Desktop version 4.62.0 through 4.67.x with Docker Model Runner using the vllm-metal backend to load models from remote registries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.68.0 or later
Fixed in 4.68.0
Interim mitigation

Disable trust_remote_code=True by default or implement strict validation before enabling it, and run the inference backend within a properly isolated sandbox to prevent host compromise.

Recommended fix High confidence

Docker Desktop 4.68.0 or later

  1. 1. Backup any important data and stop Docker Desktop
  2. 2. Upgrade Docker Desktop to version 4.68.0 or later
  3. 3. Restart Docker Desktop after the upgrade
  4. 4. Verify the upgrade was successful by checking the Docker Desktop version in the UI or running `docker version`

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Docker Desktop Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5817 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5817 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data