openclaw
Affected
- introduced
2026.3.22, fixed2026.3.31(semver)
Fixed versions
2026.3.31
Fix
- Fixed version
2026.3.31npm install [email protected]
Advisory
Also known as: CVE-2026-41301
OpenClaw: Forged Nostr DMs could create pairing state before signature verification
Summary
Before OpenClaw 2026.3.31, the Nostr DM ingress path could issue pairing challenges before validating the event signature. A forged DM could create a pending pairing entry and trigger a pairing-reply attempt before signature rejection.
Impact
An unauthenticated remote sender could consume shared pairing capacity and trigger bounded relay/logging work on the Nostr channel. This issue did not grant message decryption, pairing approval, or broader authorization bypass.
Affected Packages / Versions
openclaw (npm)>= 2026.3.22, < 2026.3.31>= 2026.3.312026.4.1Fix Commit(s)
4ee742174f36b5445703e3b1ef2fbd6ae6700fa4 — verify inbound DM signatures before pairing repliesRelease Process Note
The fix shipped in OpenClaw 2026.3.31 on March 31, 2026. The current published npm release 2026.4.1 from April 1, 2026 also contains the fix.
Thanks @smaeljaish771 for reporting.
Medium Basis: The source's own band: MODERATE
2026.3.22, fixed 2026.3.31 (semver)2026.3.31
2026.3.31npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0