GHSA-99qw-6mr3-36qr
GHSA-99qw-6mr3-36qr is a CWE-829 vulnerability in openclaw. O3 Security confirms whether GHSA-99qw-6mr3-36qr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw: Workspace plugin auto-discovery allowed code execution from cloned repositories
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
openclawnpmDescription
Summary
OpenClaw automatically discovered and loaded plugins from .openclaw/extensions/ inside the current workspace without an explicit trust or install step. A malicious repository could include a crafted workspace plugin that executed as soon as a user ran OpenClaw from that cloned directory.
Impact
Opening or running OpenClaw in an untrusted repository could lead to arbitrary code execution under the user's account.
Affected versions
openclaw <= 2026.3.11
Patch
Fixed in openclaw 2026.3.12. Workspace plugin loading now requires explicit trusted state before execution. Users should update to 2026.3.12 or later and avoid running OpenClaw inside untrusted repositories on older releases.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.3.12 |
Detection & mitigation playbook
Open-source dependencyDetect
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.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-99qw-6mr3-36qr 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-99qw-6mr3-36qr 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-99qw-6mr3-36qr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-99qw-6mr3-36qr in your dependencies?
O3 detects GHSA-99qw-6mr3-36qr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.