CVE-2026-41346: OpenClaw Remote Code Execution Vulnerability

MODERATE
Advisory Identifier: GHSA-wwfp-w96m-c6x8
CVSS 5.3
CWE-799
Published
Advisory Summary

CVE-2026-41346 is a MODERATE (CVSS 5.3) remote code execution vulnerability (CWE-799: Improper Control of Interaction Frequency) affecting OpenClaw libraries in the npm ecosystem. The issue involves pairing pending-request caps were enforced per channel instead of per account. Remediation is available by upgrading affected packages to version 2026.3.31.

CVE-2026-41346 at a Glance

CVE Identifier CVE-2026-41346
GHSA Identifier GHSA-wwfp-w96m-c6x8
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-799: Improper Control of Interaction Frequency
Affected Product OpenClaw
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2026-41346

To remediate this vulnerability, upgrade all affected OpenClaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openclaw fixed: 2026.3.31
npm install openclaw@2026.3.31
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls openclaw

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-41346, inspect your project dependencies using npm:

npm ls openclaw

Analyze the terminal output to locate any version of OpenClaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.3.31), your application is affected.

Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-799: Improper Control of Interaction Frequency, where the product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests. In OpenClaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary Before OpenClaw 2026.3.31, pending pairing-request caps were enforced per channel file instead of per account. On multi-account channel setups, requests from other accounts could fill the shared pending window and block new pairing challenges on an unaffected account. ## Impact This issue could deny new pairing or onboarding on another account until an existing request was approved or expired. It was an availability-only bug; it did not allow cross-account approval, data access, or authorization bypass. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `>= 2026.2.26, < 2026.3.31` - Patched versions: `>= 2026.3.31` - Latest published npm version: `2026.4.1` ## Fix Commit(s) - `9bc1f896c8cd325dd4761681e9bdb8c425f69785` — scope pending request caps per account ## 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.

CVE-2026-41346 Affected OpenClaw Versions

1 component(s)
Fixed Versions:
2026.3.31
Product / Package Ecosystem Affected Versions Fixed Version
openclaw
npm
≥ 2026.2.26
< 2026.3.31
2026.3.31

References

Frequently Asked Questions

What is CVE-2026-41346?
CVE-2026-41346 is a security vulnerability in OpenClaw involving Pairing pending-request caps were enforced per channel instead of per account under CWE-799: Improper Control of Interaction Frequency.
Which OpenClaw versions are affected?
Affected versions include releases prior to 2026.3.31 across affected packages: openclaw.
What version fixes CVE-2026-41346?
Upgrading to 2026.3.31 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openclaw affected?
Yes, openclaw is affected in releases prior to 2026.3.31. Upgrade your dependency to 2026.3.31 or later.
What is the CVSS score of CVE-2026-41346?
CVE-2026-41346 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-41346?
CVE-2026-41346 is classified under CWE-799: Improper Control of Interaction Frequency (The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests.).
How can I check npm dependencies for CVE-2026-41346?
Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wwfp-w96m-c6x8",
  "modified" : "2026-05-06T23:25:01Z",
  "published" : "2026-04-07T18:14:44Z",
  "aliases" : [ "CVE-2026-41346" ],
  "summary" : "OpenClaw: Pairing pending-request caps were enforced per channel instead of per account",
  "details" : "## Summary\n\nBefore OpenClaw 2026.3.31, pending pairing-request caps were enforced per channel file instead of per account. On multi-account channel setups, requests from other accounts could fill the shared pending window and block new pairing challenges on an unaffected account.\n\n## Impact\n\nThis issue could deny new pairing or onboarding on another account until an existing request was approved or expired. It was an availability-only bug; it did not allow cross-account approval, data access, or authorization bypass.\n\n## Affected Packages / Versions\n\n- Package: `openclaw` (npm)\n- Affected versions: `>= 2026.2.26, < 2026.3.31`\n- Patched versions: `>= 2026.3.31`\n- Latest published npm version: `2026.4.1`\n\n## Fix Commit(s)\n\n- `9bc1f896c8cd325dd4761681e9bdb8c425f69785` — scope pending request caps per account\n\n## Release Process Note\n\nThe 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.\n\nThanks @smaeljaish771 for reporting.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2026.2.26"
      }, {
        "fixed" : "2026.3.31"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-wwfp-w96m-c6x8"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-41346"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/9bc1f896c8cd325dd4761681e9bdb8c425f69785"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/openclaw-denial-of-service-via-improper-pending-pairing-request-cap-enforcement"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-799" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-07T18:14:44Z",
    "nvd_published_at" : null
  }
}