VIR Vulnerability Intelligence Relay

CVE-2026-41346

high
Published 2026-04-23 · Modified 2026-05-06
💬 Discuss on Community ✚ Propose mitigation
CVSS v3
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CVSS v4 NEW
6.3
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
VIR risk
7.5

Description

OpenClaw: Pairing pending-request caps were enforced per channel instead of per account

Predictions

Exploit likelihood
83%
Patch ETA
—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

Package impact
EcosystemPackageVulnerableFixed
npm npmopenclaw>=2026.2.26,<2026.3.312026.3.31
npm NPMopenclaw>= 2026.2.26, < 2026.3.312026.3.31

Application impact
VendorProductVersionsFixed
openclawopenclaw{"startIncluding":"2026.2.26","endExcluding":"2026.3.31"}2026.3.31

References

CWEs

CWE-799

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.