How severe is GHSA-m7x8-2w3w-pr42?

No CVSS score has been assigned to GHSA-m7x8-2w3w-pr42 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m7x8-2w3w-pr42?

GHSA-m7x8-2w3w-pr42 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-m7x8-2w3w-pr42?

Update openclaw to 2026.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m7x8-2w3w-pr42 is resolved across your whole dependency graph.

How do I detect GHSA-m7x8-2w3w-pr42 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m7x8-2w3w-pr42 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-m7x8-2w3w-pr42?

O3 pinpoints whether GHSA-m7x8-2w3w-pr42 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m7x8-2w3w-pr42 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m7x8-2w3w-pr42 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-m7x8-2w3w-pr42?

GHSA-m7x8-2w3w-pr42 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-m7x8-2w3w-pr42?

GHSA-m7x8-2w3w-pr42 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-m7x8-2w3w-pr42 published, and has it been updated?

GHSA-m7x8-2w3w-pr42 was published on February 18, 2026 and was last updated on February 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-m7x8-2w3w-pr42

OpenClaw has a command injection in maintainer clawtributors updater

Also known asCVE-2026-26323

Published

Feb 18, 2026

Updated

Feb 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk74th percentile+1.65%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.3Mdownloads / week

Description

Summary

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

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.

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.

Fix

Fix commit: a429380e337152746031d290432a4b93aa553d55
Planned patched version: 2026.2.14

Credits

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.1.8&&< 2026.2.14	2026.2.14

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m7x8-2w3w-pr42 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m7x8-2w3w-pr42 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m7x8-2w3w-pr42. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Command injection in the maintainer/dev script `scripts/update-clawtributors.ts`. ### 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. ### Affected Versions - Source checkouts: tags `v2026.1.8` through `v2026.2.13` (inclusive) - Version range (structured): `>= 2026.1.8, < 2026

O3 Security · Impact-Aware SCA

Is GHSA-m7x8-2w3w-pr42 in your dependencies?

O3 detects GHSA-m7x8-2w3w-pr42 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works