How severe is GHSA-r77c-2cmr-7p47?

No CVSS score has been assigned to GHSA-r77c-2cmr-7p47 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r77c-2cmr-7p47?

GHSA-r77c-2cmr-7p47 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-r77c-2cmr-7p47?

Update openclaw to 2026.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r77c-2cmr-7p47 is resolved across your whole dependency graph.

How do I detect GHSA-r77c-2cmr-7p47 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-r77c-2cmr-7p47 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-r77c-2cmr-7p47?

O3 pinpoints whether GHSA-r77c-2cmr-7p47 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-r77c-2cmr-7p47 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r77c-2cmr-7p47 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-r77c-2cmr-7p47 published, and has it been updated?

GHSA-r77c-2cmr-7p47 was published on April 17, 2026 and was last updated on May 12, 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-r77c-2cmr-7p47

GHSA-r77c-2cmr-7p47 is a security vulnerability in openclaw. O3 Security confirms whether GHSA-r77c-2cmr-7p47 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Delivery queue recovery could lose group tool-policy context for media replay

Also known asCVE-2026-43583

Published

Apr 17, 2026

Updated

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

Delivery queue recovery could lose group tool-policy context for media replay.

Affected Packages / Versions

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

Impact

Recovered queued outbound media could be replayed without the original session context needed to enforce group tool policy, weakening channel media restrictions after restart/recovery.

Technical Details

The fix persists and replays the relevant session context with delivery queue entries so recovered media dispatch goes through the same policy checks.

Fix

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

Fix Commit(s)

48aae82bbc19ba8b0741e61a08063eb0d1df464e
PR: #66025

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.10&&< 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-r77c-2cmr-7p47 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-r77c-2cmr-7p47 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-r77c-2cmr-7p47. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Delivery queue recovery could lose group tool-policy context for media replay. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `>= 2026.4.10 < 2026.4.14` - Patched versions: `>= 2026.4.14` ## Impact Recovered queued outbound media could be replayed without the original session context needed to enforce group tool policy, weakening channel media restrictions after restart/recovery. ## Technical Details The fix persists and replays the relevant session context with delivery queue entries so recovered media dispatch goes through the sa

O3 Security · Impact-Aware SCA

Is GHSA-r77c-2cmr-7p47 in your dependencies?

O3 detects GHSA-r77c-2cmr-7p47 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