Skip to main content
VulnerabilityPublished Updated

CVE-2026-41385: OpenClaw Nostr privateKey config redaction bypass leaks plaintext signing key via config.get

Affects openclawSource GCVE Database

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2026.3.31 when convenient.

Data as of 27 Oct 2026, 01:55 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2026.3.31
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade openclaw to 2026.3.31.

Affected software

ProductAffectedFixed in
npmopenclawAffected
  • <2026.3.31
Fixed in
  • 2026.3.31

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to OpenClaw version 2026.3.31 or later, where the vulnerability is fixed. The fix is officially released and available. No additional mitigation steps are required once the upgrade is applied.

Description

OpenClaw versions up to 2026.3.28 have a vulnerability where the Nostr privateKey is modeled as a plain string, allowing config views to expose the plaintext signing key via config.get. This redaction bypass leaks sensitive private key material. The issue is fixed in version 2026.3.31.

References

Community reviews

Loading reviews…