CVE-2026-126330 · Runtime
NO FIX YET
Docker Sandboxes keeps the original publish request after an operator removes a host-port mapping, so a later port change or sandbox restart republishes the service on a new host port. An attacker who can reach that restored endpoint may regain access to the service it exposes.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running Docker Sandboxes that publish sandbox services to a host port. Exposure is limited to the original bind address, which defaults to loopback, so setups that only bind to loopback face much less risk. Teams that never publish sandbox ports can skip it.
Not affected if default-config, no-port-publishing
Who cares docker, docker-sandboxes, self-hosted
docker sandbox version (or check the Docker Sandboxes version in Docker Desktop) and compare against 0.53.0Unknown from the sources.
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.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.