Quick answers
- Is CVE-2026-24763 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-24763 being exploited in the wild.
- How severe is CVE-2026-24763?
- Low severity, with a CVSS score of 3.1, published 2 February 2026.
- Which products and versions are affected?
- clawdbot (npm) SEMVER:introduced=0,fixed=2026.1.29.
- Is there a fix for CVE-2026-24763?
- Yes. clawdbot (npm): upgrade to 2026.1.29 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-24763 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-24763?
- Check whether you run clawdbot (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- clawdbot (npm): upgrade to 2026.1.29 or later
npm install clawdbot@2026.1.29
Technical details
The vulnerability is an OS command injection flaw (CWE-78) in Clawdbot's Docker sandbox execution mechanism, caused by unsafe handling of the PATH environment variable when constructing shell commands. An authenticated attacker can control environment variables supplied to the container, allowing them to influence command execution within the sandbox context. The attack requires network access and valid authentication credentials, but no user interaction. Successful exploitation enables arbitrary command execution, container filesystem access, environment variable disclosure, and potential privilege escalation in misconfigured environments. A patch was released in version 2026.1.29; all versions up to 2026.1.24 are affected.
Affected products
- OpenClaw Clawdbot <= 2026.1.24
Identifiers
- CVE-2026-24763
- GHSA-mc68-q9jw-2h3v
Timeline
- 2026-02-02: disclosed
- 2026-01-31: patched: Patched in version 2026.1.29