ZeroHour

Search: “Docker”

4 stories in the last 24h

Docker Sandboxes Vulnerabilities Let Malicious Guests Escape Workspace and Access Host Files

Docker fixed two symlink-race flaws in Docker Sandboxes, CVE-2026-77179 and CVE-2026-79994, letting malicious guests escape the workspace and read host files; fixed in 0.42.0.

Docker patched CVE-2026-77179 (Critical) and CVE-2026-79994 (High) in Docker Sandboxes 0.42.0, released September 7. Both are time-of-check-to-time-of-use symlink races: CVE-2026-77179 in the macOS virtio-fs host server (versions 0.28.0 to before 0.42.0) can allow a malicious guest to read or modify arbitrary host files and potentially achieve code execution, while CVE-2026-79994 in the guest-to-host Unix socket relay (0.37.0 to before 0.42.0) can redirect host connections to arbitrary AF_UNIX sockets. Docker recommends upgrading and, as interim mitigation, using clone mode and avoiding read-write host mounts.

Critical Docker Sandbox Vulnerabilities Enable Malicious Guests to Escape Isolated microVM Workspacesnew

Docker patched two sandbox-escape flaws, CVE-2026-77179 and CVE-2026-79994, letting malicious guest workloads access host files and sockets.

Docker fixed CVE-2026-77179 (Critical), a virtio-fs symlink race in Docker Sandboxes 0.28.0 through before 0.42.0 on macOS that could let a guest read or modify arbitrary host files and potentially reach code execution, and CVE-2026-79994 (High), a time-of-check-to-time-of-use flaw in the guest-to-host Unix socket relay affecting 0.37.0 through before 0.42.0. Fixes shipped in Docker Sandboxes 0.42.0, released September 7; Docker recommends clone mode and avoiding read-write host mounts as interim mitigations. The article also references the earlier destination-escape flaw CVE-2026-17106 in docker cp, fixed in Docker Desktop 4.86.0. No exploitation is reported.

One Compromised Kubernetes Node Can Expose Every Workload Identity Running on It

Unit42 researchers show a root attacker on a Kubernetes node can manipulate cgroups to make the local SPIRE agent issue other workloads' identities.

Palo Alto Networks Unit42 demonstrated that an attacker with root access on a Kubernetes node can alter Linux cgroup data so the local SPIRE agent matches a target pod's selectors and issues its SVID to an attacker-controlled process. The technique affects SPIFFE/SPIRE deployments, which assume node trustworthiness, and means every workload identity on a compromised node should be considered exposed. Researchers have not observed the method in the wild and released Spooffe, a testing tool to measure node identity exposure.

When Agents Look Like Beacons: NIDS Evasion by Model Context Protocol Traffic

Research shows Model Context Protocol agent traffic structurally resembles C2 beaconing and evades Suricata signatures and RITA behavioral scoring in testbeds.

An arXiv study demonstrates that Model Context Protocol (MCP) JSON-RPC traffic over Streamable HTTP mimics the polling patterns of C2 frameworks like Cobalt Strike and is not flagged as anomalous by standard enterprise defenses. In a Docker testbed with eleven traffic profiles across three TLS conditions, Suricata with the Emerging Threats Open ruleset produced near-zero alerts and RITA assigned a consistent 0.0 beacon score, regardless of jitter or TLS inspection. The authors propose an agent-native network indication standard using Agent-Native ALPN and out-of-band headers.

arXiv cs.CR · 18h agoResearch1