How severe is GHSA-8m9v-xpgf-g99m?

No CVSS score has been assigned to GHSA-8m9v-xpgf-g99m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8m9v-xpgf-g99m?

GHSA-8m9v-xpgf-g99m affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-8m9v-xpgf-g99m?

Update openclaw to 2026.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8m9v-xpgf-g99m is resolved across your whole dependency graph.

How do I detect GHSA-8m9v-xpgf-g99m in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8m9v-xpgf-g99m 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-8m9v-xpgf-g99m?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8m9v-xpgf-g99m can be triaged on real exposure rather than presence alone.

Is GHSA-8m9v-xpgf-g99m actively exploited in the wild?

No public exploit code has been indexed for GHSA-8m9v-xpgf-g99m 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.

When was GHSA-8m9v-xpgf-g99m published, and has it been updated?

GHSA-8m9v-xpgf-g99m was published on March 2, 2026 and was last updated on March 4, 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

Not in CISA KEV

GHSA-8m9v-xpgf-g99m — openclaw

GHSA-8m9v-xpgf-g99m is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw has an unauthorized sender bypass in its stop triggers and /models command authorization

Published

Mar 2, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.8Mdownloads / week

Description

Summary

Unauthorized senders could trigger two command paths without sender authorization checks:

stop-like natural-language abort triggers
/models command output

Impact

An unauthorized sender could disrupt active sessions and view model/auth metadata that should be authorization-gated.

Fix

Sender authorization is now enforced for stop-like abort triggers and /models listings.

Affected and Patched Versions

Affected: <= 2026.2.26
Patched: 2026.3.1

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.3.1`npm install openclaw@2026.3.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8m9v-xpgf-g99m 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8m9v-xpgf-g99m can be triaged on real exposure rather than presence alone.

Tailored to GHSA-8m9v-xpgf-g99m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Unauthorized senders could trigger two command paths without sender authorization checks: 1. stop-like natural-language abort triggers 2. `/models` command output ### Impact An unauthorized sender could disrupt active sessions and view model/auth metadata that should be authorization-gated. ### Fix Sender authorization is now enforced for stop-like abort triggers and `/models` listings. ### Affected and Patched Versions - Affected: `<= 2026.2.26` - Patched: `2026.3.1`

O3 Security · Impact-Aware SCA

Is GHSA-8m9v-xpgf-g99m in your dependencies?

O3 Security finds GHSA-8m9v-xpgf-g99m across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works