CVE-2026-41301: OpenClaw · Improper Verification of Cryptographic Signature
Affects OpenClawSource GCVE Database
Not known to be exploited · CVSS 6.9 Medium.
Data as of 12 Nov 2026, 01:19 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.9 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.3 |
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenClaw OpenClaw | Affected
| Fixed in– |
AI-suggested
Until a fix is available, monitoring for unusual pairing activity and limiting exposure of the Nostr DM ingress path may help mitigate risk.
Description
OpenClaw version 2026.3.22 has a vulnerability in its Nostr DM ingress path where signature verification can be bypassed. This allows unauthenticated remote attackers to send forged direct messages that create pending pairing entries and trigger pairing-reply attempts. The flaw leads to consumption of shared pairing capacity and causes bounded relay and logging activity on the Nostr channel.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-h43v-27wg-5mf9 (opens in a new tab)
- github.com/openclaw/openclaw/commit/4ee742174f36b5445703e3b1ef2fbd6ae6700fa4 (opens in a new tab)
- vulncheck.com/advisories/openclaw-forged-nostr-dm-pairing-state-creation-via-signature-verification-bypass (opens in a new tab)