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. 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-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 pinpoints whether GHSA-8m9v-xpgf-g99m 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-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

GHSA-8m9v-xpgf-g99m

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

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

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

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.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 pinpoints whether GHSA-8m9v-xpgf-g99m 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-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 detects GHSA-8m9v-xpgf-g99m 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