CVE-2025-4095

The vulnerability in Docker Desktop for macOS involves the Registry Access Management (RAM) feature, which is designed to restrict container registry access to approved hosts via DNS-level filtering [1]. When administrators use a macOS configuration profile to enforce organization sign-in, RAM policies are not applied, effectively bypassing the intended restrictions [1].

To exploit this, an attacker must be a Docker Desktop user on a macOS system where a configuration profile enforces sign-in. The attacker can then pull images from any registry, including unapproved and potentially malicious sources, despite administrator-configured RAM policies [1]. No additional authentication is required beyond the standard sign-in.

The impact is a loss of supply chain security, as users may download images from unvetted registries, introducing malicious or vulnerable software into their environments. This undermines the primary purpose of RAM, which is to prevent access to untrusted registries [1].

As of the publication date, no patch is available, and Docker has not released a workaround. Administrators relying on RAM for macOS devices should monitor Docker for updates and consider alternative enforcement mechanisms until a fix is provided [1].