Loading vulnerability…
CVE-2026-78122 is an insufficient access control vulnerability in Tecnativa docker-socket-proxy affecting versions up to and including 0.5.0. When the CONTAINERS environment variable is enabled, the proxy does not properly restrict several read-oriented endpoints within the Docker API /containers namespace. As a result, unauthenticated attackers with adjacent-network access to the exposed proxy can issue GET requests against container archive, export, logs, and process-inspection endpoints to retrieve sensitive data. The exposed functionality can be abused to read arbitrary files from containers, obtain container logs, inspect running processes, and download complete container filesystems as tar archives.
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 nine-file repository is an operational Bash proof of concept for CVE-2026-78122, an insufficient access-control granularity issue in Tecnativa docker-socket-proxy <= 0.5.0. The primary entry point, exploit/exploit.sh, targets a proxy configured with the commonly assumed read-only posture CONTAINERS=1 and POST=0. It demonstrates that the proxy's broad GET /containers prefix allow rule also exposes sensitive Docker Engine API subresources despite mutation requests being blocked. The exploit first confirms POST /containers/create is forbidden, enumerates containers, chooses a non-proxy target, then saves inspection metadata/environment variables, archive responses for /etc/passwd and /run/secrets/aws.env, a full filesystem export tarball, process-table JSON, and logs to loot/. The repository contains a self-contained Docker lab using tecnativa/docker-socket-proxy:v0.5.0 and an Alpine victim seeded with demonstrative credentials. verify.sh deploys both the vulnerable loopback proxy on port 2375 and a mitigated instance on port 2376, runs the PoC against the former, and prints comparative status codes. The mitigation directory provides a patched HAProxy configuration that explicitly denies archive, export, logs, top, changes, attach, and stats container paths unless dedicated ALLOW_* flags are enabled; normal container listing and inspection remain permitted. teardown.sh removes the lab while preserving collected loot.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.