{"vulnerability": "cve-2026-41579", "sightings": [{"uuid": "f06a726f-fd25-4485-8acc-a013714ab5db", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-41579", "type": "seen", "source": "https://bsky.app/profile/canartuc.com/post/3mobutr46go2p", "content": "runc released 1.4.3, 1.3.6, and 1.5.0-rc.3 on June 13 to fix CVE-2026-41579, where a malicious image with a /dev symlink could gain limited host filesystem writes. The releases also reuse one tmpfs instance when masking dirs, cutting overhead on Kubernetes nodes. Patching yet?\n#containers", "creation_timestamp": "2026-06-14T23:02:16.801049Z"}, {"uuid": "42824932-308b-48ea-9c48-fdc1da040487", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-41579", "type": "seen", "source": "https://bsky.app/profile/canartuc.com/post/3mol7lttetj2p", "content": "runc 1.3.6 is out, backporting a fix for CVE-2026-41579: a /dev symlink flaw that let a malicious image gain limited write access to the host filesystem. Container runtimes are the trust boundary, so this one matters. How quickly do runtime CVEs reach your production nodes?\n\n#security", "creation_timestamp": "2026-06-18T16:08:39.340363Z"}, {"uuid": "40cc2270-05e6-4a68-833a-688eb5f07a5a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-41579", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3mpkhuahgmo2v", "content": "CVE-2026-41579 - runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations\nCVE ID : CVE-2026-41579\n \n Published : July 1, 2026, 12:02 a.m. | 1\u00a0hour, 44\u00a0minutes ago\n \n Description : runc is a CLI tool for spawning and running containers ac...", "creation_timestamp": "2026-07-01T02:29:06.269708Z"}]}