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.
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.
openclaw (npm)>= 2026.3.22, < 2026.3.31>= 2026.3.312026.4.14ee742174f36b5445703e3b1ef2fbd6ae6700fa4 — verify inbound DM signatures before pairing repliesThe 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.
{
"severity": "MODERATE",
"cwe_ids": [
"CWE-347"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-07T18:14:39Z",
"nvd_published_at": "2026-04-21T00:16:30Z"
}