OpenClaw before 2026.3.31 stores Nostr privateKey as plaintext in configuration, allowing exposure through config.get method calls that bypass redaction mechanisms. Attackers can retrieve unredacted configuration data to obtain plaintext signing keys used for Nostr protocol operations.
References
Configurations
History
01 May 2026, 15:52
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:* | |
| First Time |
Openclaw openclaw
Openclaw |
|
| References | () https://github.com/openclaw/openclaw/commit/57700d716f660591fb6e09727f3ca8041fa48b9d - Patch | |
| References | () https://github.com/openclaw/openclaw/security/advisories/GHSA-jjw7-3vjf-fg5j - Vendor Advisory | |
| References | () https://www.vulncheck.com/advisories/openclaw-nostr-private-key-exposure-via-config-get-redaction-bypass - Third Party Advisory |
28 Apr 2026, 19:37
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-04-28 19:37
Updated : 2026-05-01 15:52
NVD link : CVE-2026-41385
Mitre link : CVE-2026-41385
CVE.ORG link : CVE-2026-41385
JSON object : View
Products Affected
openclaw
- openclaw
CWE
CWE-312
Cleartext Storage of Sensitive Information
