Docker Sandboxes up to 0.32.x DNS Resolution communication channel to intended endpoints
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 3.48 |
Summary
A vulnerability classified as problematic was found in Docker Sandboxes up to 0.32.x. Affected by this vulnerability is an unknown functionality of the component DNS Resolution Handler. Such manipulation leads to communication channel to intended endpoints. This vulnerability is listed as CVE-2026-12039. The attack must be carried out locally. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability was found in Docker Sandboxes up to 0.32.x and classified as problematic. Affected by this issue is an unknown function of the component DNS Resolution Handler. The manipulation with an unknown input leads to a communication channel to intended endpoints vulnerability. Using CWE to declare the problem leads to CWE-923. The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint. Impacted is confidentiality. CVE summarizes:
Docker Sandboxes (sbx) enforces an HTTP/S-only egress allowlist but does not apply it to DNS resolution: the per-network embedded DNS server forwards any queried name to the host resolver whenever the network is internet-connected, without consulting the policy. A workload inside a sandbox, which the threat model treats as untrusted, can therefore encode data into DNS labels for an attacker-controlled domain and exfiltrate it through a DNS covert channel, bypassing the configured allowlist.
The weakness was presented by Sophie Lemos. The advisory is available at docs.docker.com. This vulnerability is handled as CVE-2026-12039 since 06/11/2026. The exploitation is known to be easy. Local access is required to approach this attack. The technical details are unknown and an exploit is not available.
Upgrading to version 0.33.0 eliminates this vulnerability. The upgrade is hosted for download at github.com.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 0.1
- 0.2
- 0.3
- 0.4
- 0.5
- 0.6
- 0.7
- 0.8
- 0.9
- 0.10
- 0.11
- 0.12
- 0.13
- 0.14
- 0.15
- 0.16
- 0.17
- 0.18
- 0.19
- 0.20
- 0.21
- 0.22
- 0.23
- 0.24
- 0.25
- 0.26
- 0.27
- 0.28
- 0.29
- 0.30
- 0.31
- 0.32
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Communication channel to intended endpointsCWE: CWE-923
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Sandboxes 0.33.0
Timeline
06/11/2026 CVE reserved06/18/2026 Advisory disclosed
06/18/2026 VulDB entry created
06/18/2026 VulDB entry last update
Sources
Advisory: docs.docker.comResearcher: Sophie Lemos
Status: Confirmed
CVE: CVE-2026-12039 (🔒)
GCVE (CVE): GCVE-0-2026-12039
GCVE (VulDB): GCVE-100-372218
Entry
Created: 06/18/2026 17:29Changes: 06/18/2026 17:29 (69)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.