GitHub Advisoryadvisory · npm

GHSA-h43v-27wg-5mf9 OpenClaw: Forged Nostr DMs could create pairing state before signature verification

MEDIUM Published 2026-04-07 Modified 2026-04-24 Official page ↗
Aliases
CVE-2026-41301
Ecosystem
npm
Packages
openclaw
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Weaknesses
CWE-347
Reviewed
2026-04-07

Affected packages

• npm openclaw: >= 2026.3.22, < 2026.3.31 → fixed in 2026.3.31

Description

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 • Package: `openclaw` (npm) • Affected versions: `>= 2026.3.22, = 2026.3.31` • Latest published npm version: `2026.4.1` Fix Commit(s) • `4ee742174f36b5445703e3b1ef2fbd6ae6700fa4` — verify inbound DM signatures before pairing replies Release 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.

Related

Alias · CVE (1)

  • CVE-2026-41301 OpenClaw versions 2026.3.22 before 2026.3.31 contain a signature verification bypass vulnerability in the Nostr DM ingress path that allows… vulnerability

Weakness · CWE (1)

  • CWE-347 Improper Verification of Cryptographic Signature weakness

References