Read the docs

Docker Sandboxes restores removed automatically assigned port publications

Priority LOW 11CWE-672Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
Active
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Docker Sandboxes from 0.34.0 before 0.53.0 can republish a sandbox service on a new host port after an operator removes its automatically assigned host-port mapping. The daemon keeps the original publication request, so a later port change or sandbox restart publishes the service again, for both TCP and UDP mappings. A local user with low privileges who can reach the restored endpoint may regain access to the service, and the exposure is limited to the original bind address, which defaults to loopback. This flaw is classified as CWE-672.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

Docker Sandboxes can silently republish a sandbox service after an operator removes its automatically assigned host-port mapping. The daemon removes the active binding but retains the original publication request, allowing a later port change or sandbox restart to publish the service again on a new host port. An attacker able to reach the restored endpoint may regain access to the service. Both TCP and UDP mappings are affected. Exposure is limited to the original bind address, which defaults to loopback. The issue is fixed in version 0.53.0.

Why it matters now

EPSS 0.00121 1st percentileScored 2026-11-16
Fix Fixed Docker Sandboxes (Docker): 0.53.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
DockerDocker Sandboxes0.34.0 to before 0.53.00.53.0Patch availableCNA
  • Docker Sandboxes VendorDocker Affected 0.34.0 to before 0.53.0 Fixed in 0.53.0 Patch available CNA

Remediation

Update Docker Sandboxes to version 0.53.0.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA Docker Sandboxes (Docker) Fixed in 0.53.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Docker Sandboxes 0.53.0

    2 records Highest priority Priority LOW 2 LOW

    Other records, highest priority first

    • TI-2026-90396 Privilege escalation in Docker Sandboxes through state directoriesPriority LOW 31

Timeline

  1. 2026-11-12 Threatist record created from CVE-2026-126330
  2. 2026-11-12 Alias added: GHSA-42wc-3p53-v4wg

References

  • TI-2019-11833 Docker Desktop flaw lets local users gain privileges KEVCVSS 3.1HIGH 7.8
  • TI-2019-04061 runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows… CVSS 3.1HIGH 8.6
  • TI-2025-08316 Docker Desktop allows unauthenticated access to Docker Engine API from containers CVSS 4.0CRITICAL 9.3
  • TI-2025-02823 Elevation of Privilege in Docker Desktop for Windows during Upgrade due to Insecure Directory Deletion CVSS 4.0HIGH 7.3
  • TI-2026-14229 Tar extraction in moby/go-archive can write outside the destination directory via link following CVSS 4.0HIGH 7.1
  • TI-2023-21271 Docker Machine through 0.16.2 allows an attacker, who has control of a worker node, to… CVSS 3.1MEDIUM 6.5
See all 137 →

Sources