Skip to content

OpenClaw/Clawdbot Docker Execution has Authenticated Command Injection via PATH Environment Variable

High severity GitHub Reviewed Published Jan 31, 2026 in openclaw/openclaw • Updated Feb 3, 2026

Package

npm clawdbot (npm)

Affected versions

<= 2026.1.24

Patched versions

2026.1.29

Description

Summary

A Command Injection vulnerability existed in Clawdbot’s Docker sandbox execution mechanism due to unsafe handling of the PATH environment variable when constructing shell commands.

An authenticated user able to control environment variables could influence command execution within the container context.
This issue has been fixed and regression tests have been added to prevent reintroduction.

Impact

In environments where Docker sandbox mode was enabled, authenticated users capable of supplying environment variables could affect the behavior of commands executed inside the container.

This could lead to:

  1. Execution of unintended commands inside the container
  2. Access to the container filesystem and environment variables
  3. Exposure of sensitive data
  4. Increased risk in misconfigured or privileged container environments

References

@steipete steipete published to openclaw/openclaw Jan 31, 2026
Published by the National Vulnerability Database Feb 2, 2026
Published to the GitHub Advisory Database Feb 2, 2026
Reviewed Feb 2, 2026
Last updated Feb 3, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(25th percentile)

Weaknesses

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. Learn more on MITRE.

CVE ID

CVE-2026-24763

GHSA ID

GHSA-mc68-q9jw-2h3v

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.