4.3Mittel

CVE-2025-4095Registry Access Management (RAM) policies not applied when sign-in enforcement is configured via a configuration profile

Docker Docker Desktop Veröffentlicht: 2025-04-29 20:16 (vor 1 Jahr)

Beschreibung

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.

Schwachstellentyp (CWE): CWE-862

Daten: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Wiedergegeben wie in der Quelle, auf Englisch.

Betroffene Produkte und Versionen

Hersteller	Produkt	Versionen
Docker	Docker Desktop	4.36.0 – < 4.41.0

Referenzen und Patches

https://docs.docker.com/security/for-admins/hardened-desktop/registry-access-management

CVSS-Score

4.3Mittel

Quelle: Docker · CVSS 4.0

Angriffsvektor: Lokal
Komplexität: Niedrig
Voraussetzungen: Vorhanden
Rechte erforderlich: Niedrig
Benutzerinteraktion: Keine
Vertraulichkeit: Keine
Integrität: Keine
Verfügbarkeit: Keine

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

Alle Scores (2)

cna	CVSS 4.0	4.3Mittel
security@docker.com	CVSS 4.0	4.3Mittel

EPSS (Ausnutzungswahrscheinlichkeit in 30 Tagen)

0.15%

höher als 4 % aller CVEs

CISA-Bewertung (SSVC)

Ausnutzung: none
Automatisierbar: no
Technische Auswirkung: partial

Zeitverlauf

ID reserviert2025-04-29
Veröffentlicht2025-04-29 20:16
Bei IP-DB eingegangen2026-10-25 00:03
Zuletzt aktualisiert2026-06-17 12:32

Vergeben von (CNA): Docker
NVD-Status: Deferred

In der Quelle ansehen: CVE.org · NVD

Benachrichtigung bei neuen Schwachstellen in diesen Produkten

E-Mail-Warnungen aktivieren

Kostenlos · mit Konto · jederzeit abbestellbar

Neue CVEs im selben Produkt — Docker / Moby

4.5Mittel

CVE-2026-121520 vor 4 Tagen

Malicious client could set xattr value outside of BuildKit state directory

Moby BuildKit

In BuildKit versions prior to v0.34.1, a malicious client with access to the BuildKit control APIs can submit a build request that sets an extended attribute on a file outside the BuildKit state directory. Extended attributes in the trusted. or security. name…

6.7Mittel

CVE-2026-121522 vor 4 Tagen

Possible panic from Git source resolver

moby BuildKit

In BuildKit versions v0.26.0 through v0.34.1, a specific build definition that resolves metadata for the same Git source reference twice can cause the BuildKit daemon to panic and crash, interrupting builds handled by that daemon. The issue is fixed in v0.34.2.

5.6Mittel

CVE-2026-121541 vor 4 Tagen

Bake filesystem path entitlements approval can be skipped in some multi-target builds

Docker Docker Buildx

In Docker Buildx versions v0.19.0 through v0.38.0, an untrusted Bake definition that builds multiple targets together may expose files accessible to the Buildx client without the expected fs.read approval. Under certain conditions, filesystem paths from some …

1.8Niedrig

CVE-2026-121542 vor 4 Tagen

Bake filesystem path entitlements approval can be skipped for path using basename prefix

Docker Docker Buildx

In Docker Buildx versions v0.19.0 through v0.38.0, an untrusted Bake definition may expose files accessible to the Buildx client without the expected fs.read approval. Under certain conditions, paths under the same parent directory as the current working dire…

7.1Hoch

CVE-2026-121614 vor 4 Tagen

Docker Sandboxes host Git executes repository-controlled programs

Docker Docker Sandboxes

Docker Sandboxes versions 0.31.0 before 0.50.0 do not neutralize repository-controlled Git configuration when running certain host-side Git commands. An attacker who can modify a host repository's Git configuration, for example through a direct-mode sandbox w…

7.3Hoch

CVE-2026-93325 vor 4 Tagen

Bake filesystem entitlement consent is skipped under --progress=rawjson in Docker Buildx

Docker Docker Buildx

Buildx bake requires the user to grant entitlements with --allow or an interactive prompt before a build reaches outside the working directory. Under --progress=rawjson that consent step is skipped.