docker-socket-proxy fails to properly gate read endpoints in the /containers Docker API namespace when the CONTAINERS environment variable is set. Attackers can use GET requests to /containers/{id}/archive, /containers/{id}/export, /containers/{id}/logs, and /containers/{id}/top to read arbitrary files and download entire container filesystems as tar archives.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Public exploits 1
- Legendile7/CVE-2026-78122-POC PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Change history 1
- First seenCVSS 8.3NVD modified 2026-10-12 16:10
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 7
- https://gist.github.com/nedlir/e4f52f88a757f02c67db1fd5dd70d732
- https://github.com/Tecnativa/docker-socket-proxy
- https://github.com/Tecnativa/docker-socket-proxy/blob/v0.5.0/haproxy.cfg#L49-L61
- https://github.com/Tecnativa/docker-socket-proxy/issues/182
- https://github.com/Tecnativa/docker-socket-proxy/pull/183
- https://www.vulncheck.com/advisories/docker-socket-proxy-through-insufficient-access-control-granularity-exposes-container-filesystems
- https://github.com/Tecnativa/docker-socket-proxy/issues/182