Loading vulnerability…
A critical vulnerability in Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x, and prior to 1.7.14, 1.8.9, and 1.9.4 allows containers using subpath volume mounts to access files and directories outside of the intended volume, including the host's filesystem. This issue affects all volume types and can be exploited even by non-privileged pods, subject to file permissions. The vulnerability arises from improper validation of subpath volume mount configurations, enabling attackers to escape the container and access or modify sensitive files on the host system.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept exploit for CVE-2017-1002101, a critical Kubernetes vulnerability that allows container escape via symlink traversal in the Kubelet's volume mount logic. The exploit consists of Kubernetes pod YAML files and helper bash scripts. The YAML files define pods with two containers: one sets up a symlink from a writable volume to a sensitive host path (such as / or /home/ubuntu), and the other triggers the Kubelet to remount the volume, causing it to follow the symlink and mount the host filesystem inside the pod. The bash scripts automate the process of deploying the exploit pod, executing commands inside the compromised container (including chrooting to the host root), and cleaning up. The exploit demonstrates both root and non-root (user 1000) escapes. The repository is structured for educational and demonstration purposes, targeting Kubernetes clusters vulnerable to CVE-2017-1002101, and highlights the severity of the issue and the need for urgent patching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.