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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r77c-2cmr-7p47 can be triaged on real exposure rather than presence alone.

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.

What is the EPSS score for GHSA-r77c-2cmr-7p47?

GHSA-r77c-2cmr-7p47 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 12th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-r77c-2cmr-7p47?

GHSA-r77c-2cmr-7p47 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

Not in CISA KEV

GHSA-r77c-2cmr-7p47 — openclaw

Fix: openclaw/openclaw#66025

GHSA-r77c-2cmr-7p47 is a CWE-862 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

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

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-r77c-2cmr-7p47.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.7Mdownloads / 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`npm install openclaw@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r77c-2cmr-7p47 can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-r77c-2cmr-7p47 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works