CVE-2026-126330Docker Sandboxes
NVD
Vulnerability Summary
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.
CVSS v4.0 Base Metrics — Score 2.4 (LOW)
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NAttack VectorLocal
Attack ComplexityLow
Attack RequirementsNone
Privileges RequiredLow
User InteractionActive
Confidentiality (Vulnerable System)Low
Integrity (Vulnerable System)None
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None
Affected & Patched Versions
- Docker Sandboxes >= 0.34.0 and < 0.53.0
- Docker Sandboxes 0.53.0
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run Docker Sandboxes and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 12, 2026Published
- Nov 17, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Docker Sandboxes CVEsYou are reading CVE-2026-126330. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsMore Docker Sandboxes CVEs
External References
Data last checked: Nov 19, 2026 04:06 UTC