CVE-2025-4095: Registry Access Management (RAM) policies not applied when sign-in enforcement is configured via a configuration profile
First published: Tue Apr 29 2025(Updated: )
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.
Credit: security@docker.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Docker Desktop |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-4095?
CVE-2025-4095 has been rated as a medium severity vulnerability.
How do I fix CVE-2025-4095?
To fix CVE-2025-4095, ensure that the RAM policies are properly enforced in MacOS configurations.
What software is affected by CVE-2025-4095?
CVE-2025-4095 affects Docker Desktop on MacOS.
What are the implications of not addressing CVE-2025-4095?
Not addressing CVE-2025-4095 could allow unauthorized access to restricted registries by developers.
When was CVE-2025-4095 reported?
CVE-2025-4095 was reported in 2025.
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/weakness
- agent/title
- agent/type
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/severity
- agent/last-modified-date
- agent/event
- collector/epss-latest
- source/FIRST
- agent/source
- agent/tags
- agent/epss
- vendor/docker
- canonical/docker desktop