# CVE-2025-4095: Missing authorization in Docker Desktop

> Docker Desktop fails to enforce Registry Access Management policies when sign-in is enforced via macOS configuration profiles, allowing users to pull unapproved images.

- **Severity:** Medium 4.3 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2025
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-2h62-wf4g-8rpr

## What is CVE-2025-4095?

CVE-2025-4095 is a medium-severity missing authorization vulnerability in Docker Desktop, published on 29 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Registry Access Management (RAM) is a security feature allowing administrators to restrict access for their developers to only allowed registries. When a MacOS configuration profile is used to enforce organization sign-in, the RAM policies are not being applied, which would allow Docker Desktop users to pull down unapproved, and potentially malicious images from any registry.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-4095 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4095 is a medium-severity missing authorization vulnerability in Docker Desktop, published on 29 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4095 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-2025-4095/ (Markdown: https://insights.sbomify.com/CVE-2025-4095/index.md)
```

## Sources

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

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