Container filesystem disclosure via blanket namespace allow
Published Aug 22, 2026 · Updated Aug 22, 2026
Access-control bypass in Tecnativa docker-socket-proxy 0 through 0.5.0 allows remote attackers to read container filesystems via HTTP GET. The HAProxy rule for CONTAINERS prefix-matches the entire /containers namespace, forwarding archive, export, logs, and top requests without subpath-specific authorization. The proxy must be reachable with CONTAINERS=1 enabled; POST=0 does not block these reads, which expose files, logs, and process arguments.
Summary
What happened
Access-control bypass in Tecnativa docker-socket-proxy 0 through 0.5.0 allows remote attackers to read container filesystems via HTTP GET. The HAProxy rule for CONTAINERS prefix-matches the entire /containers namespace, forwarding archive, export, logs, and top requests without subpath-specific authorization. The proxy must be reachable with CONTAINERS=1 enabled; POST=0 does not block these reads, which expose files, logs, and process arguments.
The record
- CVE
- CVE-2026-78122
- Published
- Aug 22, 2026
- Updated
- Aug 22, 2026
- Vendor
- Tecnativa
- Product
- docker-socket-proxy
- Classifications
- CWE-1220, T1005
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2026CVE publishedPublication date reported by the CVE source.
- Aug 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.5.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- docker-socket-proxy container filesystem read PoCfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo