# CVE-2026-126330: Docker Sandboxes host-port republication after removal

Source: https://junglewise.ai/threats/cve-2026-126330-docker-sandboxes-can-silently-republish-a-sandbox-service-after  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-12. Updated: 2026-11-12  
License: CC BY 4.0 with a link back

CVE-2026-126330 · Severity: info · Published 2026-11-12

Docker Sandboxes can silently republish a network service on a new host port after an operator removes its port mapping, even though the daemon appeared to complete the removal. An attacker able to access the restored endpoint may regain unauthorized access to the service, though exposure is limited to the loopback interface by default.

Technologies: [Docker Sandboxes](https://junglewise.ai/threats/technologies/sandboxes). Vendors: [Docker](https://junglewise.ai/threats/vendors/docker).

## Quick answers

**Is CVE-2026-126330 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-126330 being exploited in the wild.

**How severe is CVE-2026-126330?** Informational severity, published 12 November 2026.

**Which products and versions are affected?** Docker Sandboxes before 0.53.0.

**Is there a fix for CVE-2026-126330?** Yes: fixed in 0.53.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-126330 attacked?** It is attacked over the network or with local access, in a hosted service.

**Am I affected by CVE-2026-126330?** Check whether you run Docker Sandboxes at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 0.53.0

## Technical details

A logic flaw in Docker Sandboxes causes the daemon to remove an active port binding but retain the original publication request in its state. When a port change occurs or the sandbox restarts, the retained request can republish the service on a new host port without operator action. Both TCP and UDP mappings are affected. The vulnerability requires the attacker to reach the restored endpoint, which by default binds only to loopback.

## Affected products

- Docker Sandboxes before 0.53.0

## Timeline

- 2026-11-12: disclosed

## References

- [https://docs.docker.com/ai/sandboxes/](https://docs.docker.com/ai/sandboxes/)

## Related threats

- [Docker Sandboxes privilege escalation via directory ownership](https://junglewise.ai/threats/cve-2026-126329-docker-sandboxes-reuses-existing-state-and-configuration)
- [Docker Sandboxes arbitrary code execution via Git configuration](https://junglewise.ai/threats/cve-2026-121614-docker-sandboxes-versions-0-31-0-before-0-50-0-do-not-neutralize)
- [Docker Sandboxes sbx cp path traversal via symlink](https://junglewise.ai/threats/cve-2026-103916-docker-sandboxes-sbx-cp-does-not-safely-confine-host-side-paths)
- [Docker Sandboxes AF_UNIX socket symlink bypass](https://junglewise.ai/threats/cve-2026-79994-docker-sandboxes-af-unix-socket-symlink-bypass)
- [Docker Sandboxes virtio-fs symlink escape on macOS](https://junglewise.ai/threats/cve-2026-77179-docker-sandboxes-virtio-fs-symlink-escape-on-macos)