Command execution via shell-interpolated commit metadata
Published Feb 19, 2026 · Updated Feb 19, 2026
OS command injection in OpenClaw 2026.1.8 through 2026.2.13 allows attackers to execute commands through malicious commit author metadata. The clawtributors updater derives a login from git log email data and inserts it into an execSync shell command without validation. Execution requires a contributor, maintainer, or CI job to run the development script in a poisoned source checkout; routine CLI use is unaffected.
Summary
What happened
OS command injection in OpenClaw 2026.1.8 through 2026.2.13 allows attackers to execute commands through malicious commit author metadata. The clawtributors updater derives a login from git log email data and inserts it into an execSync shell command without validation. Execution requires a contributor, maintainer, or CI job to run the development script in a poisoned source checkout; routine CLI use is unaffected.
The record
- CVE
- CVE-2026-26323
- Published
- Feb 19, 2026
- Updated
- Feb 19, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2026CVE publishedPublication date reported by the CVE source.
- Feb 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2026.1.8, < 2026.2.14
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo