GHSA-jwrq-8g5x-5fhm — MEDIUM AI Security Vulnerability

Q: What is GHSA-jwrq-8g5x-5fhm?

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

Q: Is GHSA-jwrq-8g5x-5fhm actively exploited?

No confirmed active exploitation of GHSA-jwrq-8g5x-5fhm has been reported, but organizations should still patch proactively.

Q: How to fix GHSA-jwrq-8g5x-5fhm?

Update to patched version: openclaw 2026.4.14.

Q: What is the CVSS score for GHSA-jwrq-8g5x-5fhm?

No CVSS score has been assigned yet.

## 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...

Full CISO analysis pending enrichment.

Affected Systems

Package	Ecosystem	Vulnerable Range	Patched
openclaw	npm	< 2026.4.14	`2026.4.14`
2 dependents 92% patched ~1d to patch Full package profile →

Do you use openclaw? You're affected.

Severity & Risk

CVSS 3.1

N/A

EPSS

N/A

Exploitation Status

No known exploitation

Sophistication

N/A

Recommended Action

Patch available

Update openclaw to version 2026.4.14

Compliance Impact

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is GHSA-jwrq-8g5x-5fhm?

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

Is GHSA-jwrq-8g5x-5fhm actively exploited?

No confirmed active exploitation of GHSA-jwrq-8g5x-5fhm has been reported, but organizations should still patch proactively.

How to fix GHSA-jwrq-8g5x-5fhm?

Update to patched version: openclaw 2026.4.14.

What is the CVSS score for GHSA-jwrq-8g5x-5fhm?

No CVSS score has been assigned yet.

Technical Details

NVD 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 `openclaw@2026.4.14` 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.