# CVE-2025-3224: Elevation of Privilege in Docker Desktop for Windows during Upgrade due to Insecure Directory Deletion

> Local attackers can escalate privileges to SYSTEM by exploiting insecure directory deletion during Docker Desktop updates on Windows.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/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:** 28 Apr 2025
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-6233-jj46-vp44

## What is CVE-2025-3224?

CVE-2025-3224 is a high-severity vulnerability in Docker Desktop, published on 28 Apr 2025. 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

A vulnerability in the update process of Docker Desktop for Windows versions prior to 4.41.0 could allow a local, low-privileged attacker to escalate privileges to SYSTEM. During an update, Docker Desktop attempts to delete files and subdirectories under the path C:\ProgramData\Docker\config with high privileges. However, this directory often does not exist by default, and C:\ProgramData\ allows normal users to create new directories. By creating a malicious Docker\config folder structure at this location, an attacker can force the privileged update process to delete or manipulate arbitrary system files, leading to Elevation of Privilege.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-3224?

It affects 1 product.


Products: Docker Desktop.

## How do I fix CVE-2025-3224?

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

## Is CVE-2025-3224 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3224 exists.

## Other vulnerabilities in Docker Desktop

- [CVE-2024-8695](https://insights.sbomify.com/CVE-2024-8695/): Code injection in Docker Desktop (critical 9.0)
- [CVE-2024-8696](https://insights.sbomify.com/CVE-2024-8696/): Code injection in Docker Desktop (high 8.9)
- [CVE-2022-37326](https://insights.sbomify.com/CVE-2022-37326/): Path traversal in n/a (high 7.8)
- [CVE-2021-37841](https://insights.sbomify.com/CVE-2021-37841/): Missing authorization in n/a (high 7.8)
- [CVE-2024-6222](https://insights.sbomify.com/CVE-2024-6222/): Privilege escalation in Docker Desktop (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3224 and fix it if it is affected.

What it is: CVE-2025-3224 is a high-severity vulnerability in Docker Desktop, published on 28 Apr 2025. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3224 exists.

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-2025-3224/ (Markdown: https://insights.sbomify.com/CVE-2025-3224/index.md)
```

## Sources

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

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