CVE-2026-32038·Docker vulnerability
OpenClaw before 2026.2.24 contains a sandbox network isolation bypass vulnerability that allows trusted operators to join another container's network namespace. Attackers can configure the docker.network parameter with container:<id> values to reach services in target container namespaces and bypass network hardening controls.
- Severity
- critical
- Software
- Docker
- Fixed in
- 2026.2.24
- Published
- 2026-03-19
Affected versions
Until: 2026.2.24
Fixed in: 2026.2.24
How to fix this CVE
Update Docker to version 2026.2.24 or later to close a critical sandbox escape vulnerability affecting network namespace isolation. This vulnerability allows operators with container access to bypass network segmentation by specifying arbitrary container network namespaces, potentially exposing inter-container traffic and services. Immediate patching is strongly recommended due to the CVSS 9.8 critical rating and unrestricted network access requirements.
sudo dnf update docker-ce --assumeyesDefensia detects this vulnerability
How to check if you are affected
- Check installed Docker version: docker --version or docker version --format '{{.Server.Version}}'
- Verify if Docker daemon is running and accessible: docker ps to confirm you can query the container runtime
- Search Docker daemon logs for suspicious network.container parameter usage: grep -r 'docker.network.*container:' /var/lib/docker/ or check journalctl -u docker -n 500 for 'container:<id>' references in container creation events
- Confirm the fix: Re-run docker --version and verify the version is 2026.2.24 or later
FAQ
What is CVE-2026-32038?
CVE-2026-32038 is a critical sandbox isolation bypass in Docker's network namespace handling. An operator can abuse the docker.network parameter with container:<id> syntax to attach a container to another container's network namespace, circumventing network isolation controls and accessing restricted services.
Is CVE-2026-32038 being actively exploited?
No, CVE-2026-32038 is not currently listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available. However, the low barrier to exploitation makes proactive patching essential.
What versions of Docker are affected by CVE-2026-32038?
All Docker versions prior to 2026.2.24 are vulnerable. The exact earliest affected version is unknown, but users should assume any version before 2026.2.24 requires patching.
How do I check if my server is vulnerable to CVE-2026-32038?
Run 'docker --version' and compare the version against 2026.2.24. If your version is lower, you are vulnerable. Additionally, audit your container orchestration for any docker.network=container:<id> usage patterns in recent deployments.
Does Defensia detect CVE-2026-32038?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server, CVE-2026-32038 will appear in your dashboard with remediation steps.
Related Docker CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-32038. Free for 1 server.
Get started free