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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-41385: 0.21% estimated exploitation activity in the next 30 days; percentile 10.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary OpenClaw Nostr privateKey config redaction bypass leaks plaintext signing key via config.get Current Maintainer Triage - Status: open - Normalized severity: medium - Assessment: v2026.3.28 still models Nostr privateKey as plain string so config views can expose it, and the secret-schema fix is unreleased. Affected Packages / Versions - Package: openclaw (npm) - Latest published npm version: 2026.3.31 - Vulnerable version range: <=2026.3.28 - Patched versions: = 2026.3.31 - First stable tag containing the fix: v2026.3.31 Fix Commit(s) - 57700d716f660591fb6e09727f3ca8041fa48b9d — 2026-03-31T19:55:03+09:00 Release Process Note - The fix is already present in released version 2026.3.31. - This draft looks ready for final maintainer disposition or publication, not additional code-fix work. Thanks @ccreater222 for reporting.

Published by the source

2 Apr 2026, 20:58 UTC

Last modified by the source

6 May 2026, 02:51 UTC

Source last checked

26 Oct 2026, 12:51 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jjw7-3vjf-fg5j

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jjw7-3vjf-fg5j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41385

Advisory: OpenClaw Nostr privateKey config redaction bypass leaks plaintext signing key via config.get
IDs: CVE-2026-41385, GHSA-jjw7-3vjf-fg5j
Record: https://patchnext.com/advisories/cve-2026-41385 (revision 3, source checked 26 Oct 2026, 12:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.3.31. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm openclaw: affected <= 2026.3.28; fixed in 2026.3.31

## Suggested inspection (read-only)
- `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openclaw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jjw7-3vjf-fg5j (OSV record GHSA-jjw7-3vjf-fg5j lists affected ranges: npm openclaw >=0 <2026.3.31 (fixed))
- Verified: https://github.com/advisories/GHSA-jjw7-3vjf-fg5j (GitHub-reviewed advisory GHSA-jjw7-3vjf-fg5j lists affected ranges: npm openclaw >=0 <=2026.3.28)

Commands are suggestions: review each one before running it.