CVE-2026-41385
OpenClaw before 2026.3.31 stores Nostr privateKey as plaintext in …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/openclaw/openclaw/commit/57700d716f660591fb6e09727f3ca8041fa48b9d
- github.com/openclaw/openclaw/security/advisories/GHSA-jjw7-3vjf-fg5j
- www.vulncheck.com/advisories/openclaw-nostr-private-key-exposure-via-config-get-redaction-
- github.com/openclaw/openclaw/releases/tag/v2026.3.31
- github.com/advisories/GHSA-jjw7-3vjf-fg5j
- nvd.nist.gov/vuln/detail/CVE-2026-41385
- nvd.nist.gov/vuln/detail/CVE-2026-41385
- cve.org/CVERecord?id=CVE-2026-41385
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.