How severe is GHSA-49cg-279w-m73x?

GHSA-49cg-279w-m73x has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-49cg-279w-m73x?

GHSA-49cg-279w-m73x affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-49cg-279w-m73x?

Update openclaw to 2026.4.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-49cg-279w-m73x is resolved across your whole dependency graph.

How do I detect GHSA-49cg-279w-m73x 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-49cg-279w-m73x 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-49cg-279w-m73x?

O3 pinpoints whether GHSA-49cg-279w-m73x 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-49cg-279w-m73x actively exploited in the wild?

No public exploit code has been indexed for GHSA-49cg-279w-m73x 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-49cg-279w-m73x published, and has it been updated?

GHSA-49cg-279w-m73x 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-49cg-279w-m73x

MEDIUM

GHSA-49cg-279w-m73x is a medium-severity (CVSS 6.5) vulnerability in openclaw. O3 Security confirms whether GHSA-49cg-279w-m73x is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Empty approver lists could grant explicit approval authorization

Also known asCVE-2026-43574

Published

Apr 17, 2026

Updated

May 8, 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

3.1Mdownloads / week

Description

Summary

Empty approver lists could grant explicit approval authorization.

Affected Packages / Versions

Package: openclaw
Ecosystem: npm
Affected versions: < 2026.4.12
Patched versions: >= 2026.4.12

Impact

For helper-backed channels, an empty resolved approver list could be interpreted as explicit approval authorization, allowing a sender outside the normal channel authorization gate to resolve pending approvals if they knew an approval id.

Technical Details

The fix prevents empty approver lists from granting explicit approval authorization and adds regression coverage for unauthorized senders.

Fix

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

Fix Commit(s)

0a105c0900de701d2ee9f1abc96b017afbd0afdd
PR: #65714

Release Process Note

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

Credits

Thanks to @anshumanbh for reporting this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.4.12

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.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-49cg-279w-m73x 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-49cg-279w-m73x 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-49cg-279w-m73x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Empty approver lists could grant explicit approval authorization. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `< 2026.4.12` - Patched versions: `>= 2026.4.12` ## Impact For helper-backed channels, an empty resolved approver list could be interpreted as explicit approval authorization, allowing a sender outside the normal channel authorization gate to resolve pending approvals if they knew an approval id. ## Technical Details The fix prevents empty approver lists from granting explicit approval authorization and adds regression c

O3 Security · Impact-Aware SCA

Is GHSA-49cg-279w-m73x in your dependencies?

O3 detects GHSA-49cg-279w-m73x 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