How severe is GHSA-g2hm-779g-vm32?

GHSA-g2hm-779g-vm32 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-g2hm-779g-vm32?

GHSA-g2hm-779g-vm32 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-g2hm-779g-vm32?

Update openclaw to 2026.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g2hm-779g-vm32 is resolved across your whole dependency graph.

How do I detect GHSA-g2hm-779g-vm32 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-g2hm-779g-vm32 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-g2hm-779g-vm32?

O3 pinpoints whether GHSA-g2hm-779g-vm32 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-g2hm-779g-vm32 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g2hm-779g-vm32 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-g2hm-779g-vm32 published, and has it been updated?

GHSA-g2hm-779g-vm32 was published on April 17, 2026 and was last updated on May 8, 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-g2hm-779g-vm32

CRITICALFix: openclaw/openclaw#66031

GHSA-g2hm-779g-vm32 is a critical-severity (CVSS 9.1) vulnerability in openclaw. O3 Security confirms whether GHSA-g2hm-779g-vm32 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Heartbeat owner downgrade missed untrusted webhook wake events

Also known asCVE-2026-43566

Published

Apr 17, 2026

Updated

May 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm

3.1Mdownloads / week

Description

Summary

Heartbeat owner downgrade missed untrusted webhook wake events.

Affected Packages / Versions

Package: openclaw
Ecosystem: npm
Affected versions: >= 2026.4.7 < 2026.4.14
Patched versions: >= 2026.4.14

Impact

Heartbeat owner downgrade logic could skip webhook wake events carrying untrusted content, preserving owner-like execution context where the run should have been downgraded.

Technical Details

The fix includes wake and hook event reasons in owner-downgrade inspection and forces downgrade for untrusted hook wake events.

Fix

The issue was fixed in #66031. The first stable tag containing the fix is v2026.4.14, and [email protected] includes the fix.

Fix Commit(s)

31281bc92f55796817a92bc43f722cba1e77ab42
PR: #66031

Release Process Note

Users should upgrade to openclaw 2026.4.14 or newer. The latest npm release, 2026.4.14, already includes the fix.

Credits

Thanks to @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.4.7&&< 2026.4.14	2026.4.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.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g2hm-779g-vm32 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-g2hm-779g-vm32 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-g2hm-779g-vm32. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Heartbeat owner downgrade missed untrusted webhook wake events. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `>= 2026.4.7 < 2026.4.14` - Patched versions: `>= 2026.4.14` ## Impact Heartbeat owner downgrade logic could skip webhook wake events carrying untrusted content, preserving owner-like execution context where the run should have been downgraded. ## Technical Details The fix includes wake and hook event reasons in owner-downgrade inspection and forces downgrade for untrusted hook wake events. ## Fix The issue was fixed in

O3 Security · Impact-Aware SCA

Is GHSA-g2hm-779g-vm32 in your dependencies?

O3 detects GHSA-g2hm-779g-vm32 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