CVE-2026-126330 Docker Sandboxes restores removed automatically assigned port publications
Attackers reaching a restored Docker Sandboxes service can regain access because removed port mappings are not automatically removed.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Harmful if only installed
- No
- Needs a specific call
- No
- Fix
- None listed
What is CVE-2026-126330?
CVE-2026-126330 is a low-severity security feature bypass vulnerability in Docker Sandboxes, published on 12 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-672
Which versions are affected by CVE-2026-126330?
An affected version is exposed as installed. No special setting or call is needed.
How do I fix CVE-2026-126330?
No fix has been published for CVE-2026-126330 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version, and do not rely on a single control for protection. More about Security feature bypass.
Is CVE-2026-126330 being exploited?
There is no known exploitation of CVE-2026-126330 in the wild and no public exploit code.
Sources
Also known as GHSA-42wc-3p53-v4wg.