CVE-2026-35627: OpenClaw: Nostr inbound DMs could trigger unauthenticated crypto work before sender policy enforcement
OpenClaw before 2026.3.22 decrypts and dispatches inbound Nostr direct messages before it checks the sender policy or pairing. Anyone who can send a Nostr DM to the bot can force expensive crypto work, and message content is handled before authorization. Fixed in OpenClaw 2026.3.22.
Published Mar 26, 2026 · Updated Apr 10, 2026 · Analysis Oct 31, 2026
What an attacker can do
The Nostr channel receives NIP-04 encrypted DMs. In versions before the fix, extensions/nostr/src/channel.ts and nostr-bus.ts verified and decrypted each message and dispatched its content first, and only then applied the sender and pairing policy. The policy was meant to keep strangers out.
The attacker needs only a Nostr identity and a relay the bot listens on. They can send many DMs and make the host spend CPU on signature verification and decryption for each one, with no size or rate guard ahead of the work. The advisory describes this as unauthorized pre-auth computation. The CVSS 4.0 vector also shows high confidentiality and integrity impact, because content from unauthorized senders got further into dispatch than it should have. The sources do not spell out what that dispatch could do.
Teams that run OpenClaw with the Nostr channel and rely on dmPolicy or pairing to restrict who can talk to the agent are the exposed group.
Who is affected
The npm package openclaw before 2026.3.22, with the Nostr channel enabled. The advisory checked tag v2026.3.23-2 and npm 2026.3.23-2 and found the fix still present.
Check your version:
npm ls openclawopenclaw
- Ecosystem
- npm
- Affected
- < 2026.3.22
- Fixed in
- 2026.3.22
- Check
npm ls openclaw
How to fix it
Upgrade to openclaw 2026.3.22 or later.
npm install openclaw@latestThe fix is commit 1ee9611. Sender policy is now enforced before signature verification and decryption. Unknown senders in pairing mode get a pairing reply and their message body is not processed until approved. Oversized payloads are dropped, and inbound DMs are rate limited, both before decryption. The sources give no numeric limits and no workaround.
How to tell if you were hit
Look at the Nostr channel logs for a high volume of inbound DMs from pubkeys that are not paired or on your allow list, and for CPU spikes on the gateway that match them. Check whether messages from unpaired senders reached agent sessions. On a patched version, unknown senders in pairing mode receive a pairing reply instead.
Beam records the shell commands and MCP tool calls an agent makes, which helps show whether an unauthorized DM led to any action.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
Nostr inbound DM handling could perform crypto and dispatch work before sender and pairing policy enforcement, enabling unauthorized pre-auth computation.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected: < 2026.3.22
- Fixed: >= 2026.3.22
- Latest released tag checked:
v2026.3.23-2(630f1479c44f78484dfa21bb407cbe6f171dac87) - Latest published npm version checked:
2026.3.23-2
Fix Commit(s)
1ee9611079e81b9122f4bed01abb3d9f56206c77
Release Status
The fix shipped in v2026.3.22 and remains present in v2026.3.23 and v2026.3.23-2.
Code-Level Confirmation
- extensions/nostr/src/channel.ts now performs authorization before decrypting and dispatching inbound DM content.
- extensions/nostr/src/nostr-bus.ts adds pre-crypto authorization, size, and rate guardrails before expensive decrypt work.
OpenClaw thanks @kuranikaran for reporting.
Credited to kuranikaran.
Questions
- Does this let a stranger make the agent act?
The advisory says content was decrypted and dispatched before policy enforcement. It does not describe what an unauthorized message could trigger. Treat unpaired senders as untrusted and upgrade.
- Is OpenClaw 2026.3.21 affected by CVE-2026-35627?
Yes. Everything before 2026.3.22 is affected. The fix is present in 2026.3.22, 2026.3.23 and 2026.3.23-2.
- Is it exploited in the wild?
No source reports it, and it is not in CISA's KEV catalog. The EPSS score is 0.0045.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
