CVE-2026-126330

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.

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

• 2.4CVSS 4.0, Lowfrom the CNA (Docker)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

What to do

• Upgrade Docker Sandboxes to version 0.53.0 or later.CNA solution statement
• Publish services using an explicit host port instead of an automatically assigned port. Stop the listening service when withdrawing access until upgrading.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

Timeline

1. 12 Nov 2026 Published

Weakness

• CWE-672

References

• docs.docker.comproduct