Skip to main content
CVE-2026-41385VulnerabilityPublished Updated

Openclaw cli: OpenClaw Nostr privateKey config redaction bypass leaks plaintext signing key via config.get

Affects openclaw-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-41385· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 2026.3.31 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.1
CNA (VulnCheck)CVSS 3.16.5
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.31
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 16 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.31.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <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 OpenClaw CLI to version 2026.3.31 or later, where the privateKey redaction bypass is fixed. Versions prior to 2026.3.31 are vulnerable. No additional mitigation is required once updated.

Description

OpenClaw CLI versions before 2026.3.31 have a vulnerability where the Nostr privateKey is stored as a plain string and can be leaked via the config.get method, bypassing intended redaction. This exposure allows an attacker with access to configuration views to obtain the plaintext signing key. The issue is fixed in version 2026.3.31.

References

Community reviews

Loading reviews…