Is there a patch available for CVE-2026-41346?

Yes, a patch is available for CVE-2026-41346. Update the affected software to the latest version immediately.

OpenClaw CVE-2026-41346

Q: What is the CVSS score of CVE-2026-41346?

CVE-2026-41346 has a CVSS 4.0 base score of 6.3 (Medium). CVSS vector: 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.1%.

EUVD-2026-25330 MEDIUM

Improper Control of Interaction Frequency (CWE-799)

2026-04-23 VulnCheck

GHSA-mf69-r24q-ghhr

Denial Of Service Openclaw

6.3

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

6.3 MEDIUM

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

5.3 MEDIUM

Network-reachable, no authentication required; availability impact is low (pairing DoS only) with no confidentiality or integrity effect confirmed.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jul 24, 2026 - 03:25 vuln.today

Analysis Generated

Jul 24, 2026 - 03:25 vuln.today

CVSS changed

Apr 23, 2026 - 22:28 NVD

5.3 (MEDIUM) 6.3 (MEDIUM)

EUVD ID Assigned

Apr 23, 2026 - 22:15 euvd

EUVD-2026-25330

Patch released

Apr 23, 2026 - 22:15 nvd

Patch available

CVE Published

Apr 23, 2026 - 21:58 nvd

MEDIUM 6.3

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

2 npm packages depend on openclaw (2 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.2.26.

DescriptionCVE.org

OpenClaw 2026.2.26 before 2026.3.31 enforces pending pairing-request caps per channel file instead of per account, allowing attackers to exhaust the shared pending window. Remote attackers can submit pairing requests from other accounts to block new pairing challenges on unaffected accounts, causing denial of service.

AnalysisAI

Denial of service in OpenClaw versions 2026.2.26 through pre-2026.3.31 allows unauthenticated remote attackers to exhaust the shared pending pairing-request window on multi-account channel deployments, blocking legitimate accounts from initiating new pairing or onboarding. The root flaw is a quota-scoping error: the cap on pending requests was enforced per channel file rather than per account, so one actor's requests consume capacity allocated to unrelated accounts. The GHSA advisory confirms this is an availability-only impact - no cross-account data access, approval, or authorization bypass is possible. No public exploit or CISA KEV listing exists; EPSS probability is 0.10%, reflecting minimal real-world exploitation pressure at time of analysis.

Technical ContextAI

OpenClaw is an npm package (CPE: cpe:2.3:a:openclaw:openclaw) providing device-pairing and channel-onboarding workflows. The vulnerable logic resided in src/pairing/pairing-store.ts within the pruneExcessRequests function, which applied the PAIRING_PENDING_MAX cap globally against the full list of requests in a shared channel file, regardless of which account submitted each request. CWE-799 (Improper Control of Interaction Frequency) precisely describes this root cause: the frequency or quota control is misscoped, allowing one principal's consumption to crowd out another's allocation. The commit diff shows the fix renamed pruneExcessRequests to pruneExcessRequestsByAccount and introduced per-account grouping via a Map keyed on a normalized accountId, ensuring each account's pending slots are counted and pruned independently. The pairing store reads and writes JSON fixture files per channel, and the new resolvePairingRequestAccountId helper resolves legacy default-account entries gracefully.

RemediationAI

Upgrade the OpenClaw npm package to version 2026.3.31 or later - the current latest release, 2026.4.1, also contains the fix. Run npm update openclaw or update the package.json dependency to ">=2026.3.31" and reinstall. The upstream patch commit is 9bc1f896c8cd325dd4761681e9bdb8c425f69785 (https://github.com/openclaw/openclaw/commit/9bc1f896c8cd325dd4761681e9bdb8c425f69785); the vendor advisory is at https://github.com/openclaw/openclaw/security/advisories/GHSA-wwfp-w96m-c6x8. If an immediate upgrade is not possible on multi-account channel deployments, a compensating control is to restrict which external accounts are permitted to submit pairing requests at the application or network layer - for example, allowlisting known account identifiers or gating channel access behind an authenticated API proxy. This trades onboarding convenience for reduced exposure and should be treated as a temporary measure only, as the correct fix is per-account quota scoping delivered in the patch.