What is the CVSS score of CVE-2026-32038?

CVE-2026-32038 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Docker are affected by CVE-2026-32038?

A critical vulnerability in OpenClaw allows attackers with operator access to bypass network isolation controls and reach sensitive services that should be inaccessible.. A patch is available.

How to fix or mitigate CVE-2026-32038?

Within 24 hours: Inventory all OpenClaw deployments and identify systems running versions prior to 2026.2.24; restrict operator access to systems requiring OpenClaw pending remediation. Within 7 days: Implement network segmentation to isolate containers and disable the docker.network parameter across all OpenClaw instances. Within 30 days: Deploy OpenClaw version 2026.2.24 or later once patch becomes available; conduct full container network architecture audit to identify lateral movement risks.

Docker CVE-2026-32038

CRITICAL

Improper Access Control (CWE-284)

2026-03-19 disclosure@vulncheck.com

GHSA-ww6v-v748-x7g9

Authentication Bypass Docker

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

Analysis Generated

Mar 19, 2026 - 22:30 vuln.today

CVE Published

Mar 19, 2026 - 22:16 nvd

CRITICAL 9.8

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 npm packages depend on openclaw (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.2.24.

DescriptionCVE.org

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.

AnalysisAI

A sandbox network isolation bypass vulnerability in OpenClaw allows trusted operators to escape container network boundaries and join other containers' network namespaces. OpenClaw versions before 2026.2.24 are affected, enabling attackers who have operator privileges to configure the docker.network parameter with 'container:<id>' values to reach services in target container namespaces and bypass network segmentation controls. The vulnerability has a critical CVSS score of 9.8 but requires trusted operator access, and there is no evidence of active exploitation in KEV or high EPSS probability.

Technical ContextAI

OpenClaw is a container orchestration platform that implements network isolation between containers as a security boundary. The vulnerability stems from improper access control (CWE-284) in how the docker.network parameter is validated when operators configure container networking. The flaw allows operators to specify 'container:<id>' as a network configuration value, which instructs Docker to join an existing container's network namespace rather than creating an isolated network. This bypasses the intended network segmentation that prevents lateral movement between containers. While no specific CPE identifiers are provided in the available data, the affected product is OpenClaw container orchestration software.

RemediationAI

Upgrade OpenClaw to version 2026.2.24 or later which contains the fix for this vulnerability (see the GitHub security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-ww6v-v748-x7g9). As an interim mitigation, restrict operator permissions to only trusted personnel and implement additional monitoring for unusual docker.network parameter usage, particularly any containing 'container:' prefixes. Organizations should audit existing container configurations to ensure no containers are currently configured to join other containers' network namespaces inappropriately.