ICMP egress bypass via missing authorizer restoration
Published Jun 18, 2026 · Updated Jun 18, 2026
Improper ICMP egress enforcement in Docker Sandboxes before 0.33.0 allows local users to bypass network policy after a daemon restart. On daemon restart, sbx rebuilds persisted networks from disk without reapplying the ICMP authorizer installed only during network creation. An untrusted sandbox workload can then reach arbitrary hosts for reconnaissance or data exfiltration over an ICMP covert channel, regardless of the allowlist.
Summary
What happened
Improper ICMP egress enforcement in Docker Sandboxes before 0.33.0 allows local users to bypass network policy after a daemon restart. On daemon restart, sbx rebuilds persisted networks from disk without reapplying the ICMP authorizer installed only during network creation. An untrusted sandbox workload can then reach arbitrary hosts for reconnaissance or data exfiltration over an ICMP covert channel, regardless of the allowlist.
The record
- CVE
- CVE-2026-12539
- Published
- Jun 18, 2026
- Updated
- Jun 18, 2026
- Vendor
- Docker
- Product
- Docker Sandboxes
- Classifications
- CWE-665, CWE-923, T1048.003, T1018
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2026CVE publishedPublication date reported by the CVE source.
- Jun 18, 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.14.0 <0.33.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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