Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

OpenClaw: Forged Nostr DMs could create pairing state before signature verification

CVE-2026-41301GHSA-h43v-27wg-5mf9

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (openclaw 2026.3.31), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm openclaw

    Affected
    >= 2026.3.22, < 2026.3.31
    Fixed in
    2026.3.31

Sources

Severity and exploitation
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:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-41301: 0.25% estimated exploitation activity in the next 30 days; percentile 16.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Before OpenClaw 2026.3.31, the Nostr DM ingress path could issue pairing challenges before validating the event signature. A forged DM could create a pending pairing entry and trigger a pairing-reply attempt before signature rejection. Impact An unauthenticated remote sender could consume shared pairing capacity and trigger bounded relay/logging work on the Nostr channel. This issue did not grant message decryption, pairing approval, or broader authorization bypass. Affected Packages / Versions - Package: openclaw (npm) - Affected versions: = 2026.3.22, < 2026.3.31 - Patched versions: = 2026.3.31 - Latest published npm version: 2026.4.1 Fix Commit(s) - 4ee742174f36b5445703e3b1ef2fbd6ae6700fa4 — verify inbound DM signatures before pairing replies Release Process Note The fix shipped in OpenClaw 2026.3.31 on March 31, 2026. The current published npm release 2026.4.1 from April 1, 2026 also contains the fix. Thanks @smaeljaish771 for reporting.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-h43v-27wg-5mf9

  2. Revision 2 · amended ·

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

  3. Revision 1 · created ·

    Published from osv record GHSA-h43v-27wg-5mf9

Agent brief

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

# Patch Next advisory brief: CVE-2026-41301

Advisory: OpenClaw: Forged Nostr DMs could create pairing state before signature verification
IDs: CVE-2026-41301, GHSA-h43v-27wg-5mf9
Record: https://patchnext.com/advisories/cve-2026-41301 (revision 3, source checked 26 Oct 2026, 12:50 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.22, < 2026.3.31; 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-h43v-27wg-5mf9 (OSV record GHSA-h43v-27wg-5mf9 lists affected ranges: npm openclaw >=2026.3.22 <2026.3.31 (fixed))
- Verified: https://github.com/advisories/GHSA-h43v-27wg-5mf9 (GitHub-reviewed advisory GHSA-h43v-27wg-5mf9 lists affected ranges: npm openclaw >=2026.3.22 <2026.3.31)

Commands are suggestions: review each one before running it.

Loading voting…