# CVE-2026-106581: Docker Desktop for Windows installer failed to verify external packages

> Attackers can execute arbitrary code as LocalSystem by providing a crafted package to the Docker Desktop installer, bypassing signature verification.

- **Severity:** High 8.2 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-r8rf-x7cj-7933

## What is CVE-2026-106581?

CVE-2026-106581 is a high-severity code injection vulnerability in Docker Desktop, published on 9 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Before 4.92.0, Docker Desktop for Windows did not verify the signature of a package supplied to Docker Desktop Installer.exe install -package. An attacker able to provide a crafted package and convince a user to approve the Docker-signed UAC prompt could execute attacker-controlled installer actions as LocalSystem.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-106581?


## How do I fix CVE-2026-106581?

No fix has been published for CVE-2026-106581 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-106581 being exploited?

There is no known exploitation of CVE-2026-106581 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106581 and fix it if it is affected.

What it is: CVE-2026-106581 is a high-severity code injection vulnerability in Docker Desktop, published on 9 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-106581 in the wild and no public exploit code.

Affected product: Docker Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-106581/ (Markdown: https://insights.sbomify.com/CVE-2026-106581/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106581
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106581
- OSV: https://osv.dev/vulnerability/CVE-2026-106581

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-106581/
Summaries are generated and may contain mistakes; the official description above is the record.