Registry Access Management (RAM) policies not applied when sign-in enforcement is configured via a configuration profile
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Docker | Docker Desktop | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Docker | Docker Desktop | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-12619 | 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. |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.151% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Registry Access Management (RAM) policies not applied when sign-in enforcement is configured via a configuration profile | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV4_0
|