How severe is GHSA-jwrq-8g5x-5fhm?

GHSA-jwrq-8g5x-5fhm has a CVSS score of 6.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-jwrq-8g5x-5fhm?

GHSA-jwrq-8g5x-5fhm affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-jwrq-8g5x-5fhm?

Update openclaw to 2026.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jwrq-8g5x-5fhm is resolved across your whole dependency graph.

How do I detect GHSA-jwrq-8g5x-5fhm 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-jwrq-8g5x-5fhm 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-jwrq-8g5x-5fhm?

O3 pinpoints whether GHSA-jwrq-8g5x-5fhm 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-jwrq-8g5x-5fhm actively exploited in the wild?

No public exploit code has been indexed for GHSA-jwrq-8g5x-5fhm 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-jwrq-8g5x-5fhm published, and has it been updated?

GHSA-jwrq-8g5x-5fhm 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-jwrq-8g5x-5fhm

MEDIUM

GHSA-jwrq-8g5x-5fhm is a medium-severity (CVSS 6.8) vulnerability in openclaw. O3 Security confirms whether GHSA-jwrq-8g5x-5fhm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Collect-mode queue batches could reuse the last sender authorization context

Also known asCVE-2026-43535

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.2Mdownloads / week

Description

Summary

Collect-mode queue batches could reuse the last sender authorization context.

Affected Packages / Versions

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

Impact

Collect-mode queued messages from different senders could be drained as one batch using the final sender's authorization context, allowing earlier messages to inherit a more privileged context.

Technical Details

The fix splits collect-mode batches by sender authorization context before dispatch, preserving each message's own trust state.

Fix

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

Fix Commit(s)

43d4be902755c970b3d15608679761877718da69
PR: #66024

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`	all versions	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-jwrq-8g5x-5fhm 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-jwrq-8g5x-5fhm 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-jwrq-8g5x-5fhm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Collect-mode queue batches could reuse the last sender authorization context. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `< 2026.4.14` - Patched versions: `>= 2026.4.14` ## Impact Collect-mode queued messages from different senders could be drained as one batch using the final sender's authorization context, allowing earlier messages to inherit a more privileged context. ## Technical Details The fix splits collect-mode batches by sender authorization context before dispatch, preserving each message's own trust state. ## Fix T

O3 Security · Impact-Aware SCA

Is GHSA-jwrq-8g5x-5fhm in your dependencies?

O3 detects GHSA-jwrq-8g5x-5fhm 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