---
id: "CVE-2026-126330"
page: "https://infrastack.ai/live/CVE-2026-126330"
kind: "vulnerability"
aliases: ["CVE-2026-126330"]
title: "Docker Sandboxes: removed port mapping can silently republish a sandbox service"
severity: "low"
cvss: 2.4
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["docker", "docker-sandboxes", "runtime", "self-hosted"]
not_affected_if: ["default-config", "no-port-publishing"]
published_at: "2026-11-12T16:19:04+00:00"
first_seen_at: "2026-11-12T16:44:02+00:00"
updated_at: "2026-11-12T16:45:48+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-126330", "first_seen_at": "2026-11-12T16:44:02+00:00"}]
exploit_sources: []
---

# Docker Sandboxes: removed port mapping can silently republish a sandbox service

Link for people: https://infrastack.ai/live/CVE-2026-126330 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `docker sandbox version` (or check the Docker Sandboxes version in Docker Desktop) and compare against `0.53.0`
- Review sandbox port publications and confirm no service is re-published after its mapping was removed
- Confirm the publish bind address is loopback (default), not a wider interface

## Timeline

- 2026-11-12T16:44:02+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-126330

## 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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_