Project Subscriptions
No data.
No advisories yet.
Solution
Upgrade Docker Sandboxes to version 0.53.0 or later.
Workaround
Publish services using an explicit host port instead of an automatically assigned port. Stop the listening service when withdrawing access until upgrading.
| Link | Providers |
|---|---|
| https://docs.docker.com/ai/sandboxes/ |
|
Thu, 12 Nov 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Docker Sandboxes restores removed automatically assigned port publications | |
| Weaknesses | CWE-672 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Docker
Published:
Updated: 2026-11-12T15:46:29.130Z
Reserved: 2026-11-10T20:28:53.758Z
Link: CVE-2026-126330
No data.
Status : Received
Published: 2026-11-12T16:19:04.810
Modified: 2026-11-12T16:19:04.810
Link: CVE-2026-126330
No data.
OpenCVE Enrichment
No data.