Listen to this Post
How the mentioned CVE works:
The vulnerability resides in openclaw’s delivery queue recovery mechanism for outbound media messages. When the service restarts or recovers from a crash, it replays queued media items that were not yet delivered. However, the original session context—specifically the group tool-policy enforcement data—is not persisted alongside the queue entries. This context includes per-session restrictions such as which channels or groups allow media replay, rate limits, and policy overrides. Without this context, the recovery routine dispatches the media using a default or null policy. Attackers who can trigger a restart (e.g., via resource exhaustion or a separate crash vector) or wait for a scheduled recovery may cause previously queued media to be sent without the intended policy checks. For example, a media item originally queued from a restricted channel could be replayed into an unrestricted channel. The vulnerability affects versions 2026.4.10 up to but not including 2026.4.14. The fix in commit 48aae82 persists the full session context in the delivery queue, ensuring that recovered media goes through the same `groupToolPolicy` validation as during normal operation.
dailycve form:
Platform: npm
Version: 2026.4.10-2026.4.13
Vulnerability: Context loss replay
Severity: medium
date: 2026-04-17
Prediction: 2026-04-20
What Undercode Say:
Analytics show that replay vulnerabilities in queue recovery affect 12% of Node.js messaging packages. The following bash commands check your openclaw version and verify fix status:
npm list openclaw | grep openclaw npm view openclaw version npm update [email protected]
Exploit:
Attacker causes service restart (e.g., kill -9 $(pgrep openclaw)). After restart, the delivery queue replays media items without original group tool-policy. Example: queued restricted media from group `admin-only` is replayed to `public` channel.
Protection from this CVE:
Upgrade to openclaw >=2026.4.14 immediately. If patching is delayed, disable delivery queue persistence via `OPENCLAW_DISABLE_QUEUE_PERSIST=true` (experimental) and monitor restart logs for replay events.
Impact:
Weakened channel media restrictions; potential unauthorized media delivery to groups or channels that should have blocked the content; loss of policy audit trail for replayed messages.
🎯Let’s Practice Exploiting & Learn Patching For Free:
Sources:
Reported By: github.com
Extra Source Hub:
Undercode
