{"vulnerability": "CVE-2025-4095", "sightings": [{"uuid": "8a8b1237-476e-49e6-94bb-d999a75b7040", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-4095", "type": "seen", "source": "https://bsky.app/profile/skyr.chaos.social.ap.brid.gy/post/3lpbh4x5j56e2", "content": "", "creation_timestamp": "2025-05-16T06:57:45.594111Z"}, {"uuid": "acacdf4d-2643-4d62-bb92-a07f2cee58b5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-4095", "type": "seen", "source": "https://bsky.app/profile/applex4.bsky.social/post/3lol77kfgtv2b", "content": "", "creation_timestamp": "2025-05-07T10:35:35.348463Z"}, {"uuid": "85700aa4-2cde-4666-91f2-3d81ec40229b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-4095", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lny2ijzcwz2n", "content": "", "creation_timestamp": "2025-04-29T19:50:33.712068Z"}, {"uuid": "f8014aae-12a6-4531-813d-a70579d9a747", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-4095", "type": "seen", "source": "https://bsky.app/profile/dennissellers.bsky.social/post/3loiw25ytch26", "content": "", "creation_timestamp": "2025-05-06T12:46:11.981087Z"}, {"uuid": "99b8e268-c131-4f69-a6d5-9a2ebc8ab15f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-4095", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/13887", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-4095\n\ud83d\udd25 CVSS Score: 4.3 (cvssV4_0, Vector: 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)\n\ud83d\udd39 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.\n\ud83d\udccf Published: 2025-04-29T17:16:16.894Z\n\ud83d\udccf Modified: 2025-04-29T18:00:02.591Z\n\ud83d\udd17 References:\n1. https://docs.docker.com/security/for-admins/hardened-desktop/registry-access-management", "creation_timestamp": "2025-04-29T18:12:24.000000Z"}, {"uuid": "bd6bd4a0-09fa-4ecf-b4c9-7bf8ab199ea5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-4095", "type": "seen", "source": "https://t.me/cvedetector/24033", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-4095 - Docker Desktop MacOS Registry Access Bypass Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-4095 \nPublished : April 29, 2025, 6:15 p.m. | 39\u00a0minutes ago \nDescription : 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. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-29T21:01:04.000000Z"}]}