docker-socket-proxy: Insufficient Granularity of Access Control
CVE-2026-78122 is a high-severity insufficient granularity of access control vulnerability in docker-socket-proxy from Tecnativa, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected docker-socket-proxy versions: 0.5.0 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.31% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of docker-socket-proxy you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Tecnativa | docker-socket-proxy | 0.5.0 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N. Scored by CNA (vulncheck.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.3 | High | CNA (vulncheck.com) |
| CVSS 3.1 | 7.4 | High | CNA (vulncheck.com) |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insufficient Granularity of Access Control
The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack the required granularity
How developers prevent this class of flaw
- Access-control-policy protections must be reviewed for design inconsistency and common weaknesses. Access-control-policy definition and programming flow must be tested in pre-silicon, post-silicon testing.
More Insufficient Granularity of Access Control vulnerabilities (CWE-1220)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
- gist.github.com/nedlir/e4f52f88a757f02c67db1fd5dd70d732
- github.com/Tecnativa/docker-socket-proxy
- github.com/Tecnativa/docker-socket-proxy/blob/v0.5.0/haproxy.cfg#L49-L61
- github.com/Tecnativa/docker-socket-proxy/issues/182
- vulncheck.com/advisories/docker-socket-proxy-through-insufficient-access-control-granularity-exposes-containe…
Recent Insufficient Granularity of Access Control vulnerabilities
- 7.1 High severity
- 7.8 High severity
- 8.6 High severity
- 9.6 Critical severity
- 9.1 Critical severity
- 7.8 High severity
Spotted an error? Tell us.