dbcve.org
OpenclawApplication

CVE-2026-32038

CRITICAL · 9.0 CVSS v3.1 Published 2026-03-19
Fix available
A fix is available. Upgrade to 2026.2.24 or later.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OpenClaw before version 2026.2.24 contains a sandbox network isolation bypass where trusted operators can configure the docker.network parameter with container:<id> syntax to join another container's network namespace. This allows attackers to reach services running in target container namespaces, effectively bypassing implemented network hardening controls.

MitigationUpdate OpenClaw to version 2026.2.24 or later. Additionally, review and enforce network policies to restrict container-to-container communication and apply least-privilege principles to operator permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenclawApplication
Affected:< 2026.2.24

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenClaw version
    Run 'openclaw --version' or check the installed package version using your system's package manager (dpkg, rpm, pip, etc.)
    Affected if The installed version is lower than 2026.2.24
  2. Check operator permission to configure docker.network
    Review OpenClaw operator role configurations or RBAC settings to determine if any non-admin operators have permission to set or modify the docker.network parameter in container definitions
    Affected if Operators other than administrators can configure the docker.network parameter
  3. Identify container:<id> network configurations
    Search all OpenClaw container configuration files, manifests, or the configuration database for entries containing 'docker.network' set to 'container:' syntax (e.g., container:<container_id>)
    Affected if Any container configurations use the container:<id> syntax to join another container's network namespace
  4. Verify network isolation policies
    Inspect OpenClaw's network policy definitions or network security group configurations to confirm whether explicit deny rules exist for inter-container communication
    Affected if No network policies exist to block container-to-container network joins, or policies can be bypassed via the container:<id> syntax
  5. Audit recent container network join operations
    Review OpenClaw audit logs or container runtime logs for any recent operations where docker.network was set using container:<id> syntax to join external container namespaces
    Affected if Historical or current container configurations show use of the container:<id> syntax to join other containers' networks

You are affected if OpenClaw version is below 2026.2.24 AND operators can configure docker.network with container:<id> syntax, as this allows bypassing network isolation between containers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.2.24 or later
Fixed in 2026.2.24
Interim mitigation

Update OpenClaw to version 2026.2.24 or later. Additionally, review and enforce network policies to restrict container-to-container communication and apply least-privilege principles to operator permissions.

Recommended fix High confidence

OpenClaw 2026.2.24 or later

  1. Identify the current OpenClaw installation method (Docker container, package manager, or source compilation)
  2. Stop the running OpenClaw service or container
  3. If using Docker, pull the updated OpenClaw image with version 2026.2.24 or later: docker pull openclaw/openclaw:2026.2.24 or newer
  4. If using a package manager, check for available updates and install version 2026.2.24 or later
  5. If compiled from source, pull the latest code from the repository and rebuild
  6. Review the docker.network parameter configuration in your deployment to ensure container:<id> values are not being used to bypass network isolation
  7. Restart the OpenClaw service with the updated version
  8. Verify the upgrade was successful by checking the OpenClaw version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32038 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32038 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data