CVE-2026-26323

CVE-2026-26323 is a high-severity OS command injection vulnerability in openclaw (npm), affecting versions >= 2026.1.8, < 2026.2.14. It is fixed in 2026.2.14.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

OpenClaw has a command injection in maintainer clawtributors updater

Command injection in the maintainer/dev script scripts/update-clawtributors.ts.

Affected Versions

  • Source checkouts: tags v2026.1.8 through v2026.2.13 (inclusive)
  • Version range (structured): >= 2026.1.8, < 2026.2.14

Details

The script derived a GitHub login from git log author metadata and interpolated it into a shell command (via execSync). A malicious commit record could inject shell metacharacters and execute arbitrary commands when the script is run.

Credits

Thanks @scanleale and @MegaManSec (https://joshua.hu) of AISLE Research Team for reporting.

Impact

Affects contributors/maintainers (or CI) who run bun scripts/update-clawtributors.ts in a source checkout that contains a malicious commit author email (e.g. crafted @users.noreply.github.com values).

Normal CLI usage is not affected (npm i -g openclaw): this script is not part of the shipped CLI and is not executed during routine operation.

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

Affected versions

openclaw (>= 2026.1.8, < 2026.2.14)

Security releases

openclaw → 2026.2.14 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

  • Fix commit: a429380e337152746031d290432a4b93aa553d55
  • Planned patched version: 2026.2.14

Frequently Asked Questions

  1. What is CVE-2026-26323? CVE-2026-26323 is a high-severity OS command injection vulnerability in openclaw (npm), affecting versions >= 2026.1.8, < 2026.2.14. It is fixed in 2026.2.14. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
  2. Which versions of openclaw are affected by CVE-2026-26323? openclaw (npm) versions >= 2026.1.8, < 2026.2.14 is affected.
  3. Is there a fix for CVE-2026-26323? Yes. CVE-2026-26323 is fixed in 2026.2.14. Upgrade to this version or later.
  4. Is CVE-2026-26323 exploitable, and should I be worried? Whether CVE-2026-26323 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2026-26323 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2026-26323? Upgrade openclaw to 2026.2.14 or later.

Other vulnerabilities in openclaw

Stop the waste.
Protect your environment with Kodem.