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

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

OpenClaw CVE-2026-41377

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

CVE-2026-41377 has a CVSS 4.0 base score of 5.1 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/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.0%.

EUVD-2026-26086 MEDIUM

Not Failing Securely ('Failing Open') (CWE-636)

2026-04-28 VulnCheck

Information Disclosure Openclaw

5.1

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.1 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Scope

Lifecycle Timeline

Analysis Generated

Apr 28, 2026 - 20:06 vuln.today

CVSS changed

Apr 28, 2026 - 19:52 NVD

4.6 (MEDIUM) 5.1 (MEDIUM)

EUVD ID Assigned

Apr 28, 2026 - 19:30 euvd

EUVD-2026-26086

Analysis Generated

Apr 28, 2026 - 19:30 vuln.today

Patch released

Apr 28, 2026 - 19:30 nvd

Patch available

CVE Published

Apr 28, 2026 - 18:09 nvd

MEDIUM 5.1

Blast Radius

ecosystem impact

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

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

Ecosystem-wide dependent count for version 2026.3.31.

DescriptionCVE.org

OpenClaw before 2026.3.31 contains a fail-open vulnerability in the plugin installation flow where security scan failures do not block installation. Attackers can exploit scan failures to install untrusted plugins when operators proceed despite visible scan warnings.

AnalysisAI

OpenClaw before version 2026.3.31 fails to block plugin installation when security scans detect threats, allowing authenticated users to install malicious plugins by ignoring visible scan warnings. The vulnerability requires user interaction (UI:P) and authenticated access (PR:L), but enables installation of untrusted code with moderate integrity impact when exploited.

Technical ContextAI

OpenClaw's plugin installation flow implements security scanning as an advisory check rather than a mandatory gate. The vulnerability is classified as CWE-636 (Weak Access Control in Plugin Installation), which describes systems that fail to properly enforce security controls during extension or plugin loading. When the security scan process detects suspicious indicators in a plugin package, the system displays a warning but permits the operator to proceed unconditionally. This fail-open design treats scan failures as informational rather than blocking, allowing bypassing of intended security validation. The affected CPE range cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:* indicates all versions before 2026.3.31 are vulnerable.

RemediationAI

Upgrade OpenClaw to version 2026.3.31 or later, which implements proper enforcement of security scan results as a mandatory installation gate. Upstream fixes are available via multiple commits referenced in the GitHub advisory (commits 7a953a5, 44b9936, 0d7f1e2, bf96c67) that enforce scan-blocking logic. Until patching is complete, operators should implement administrative controls: disable plugin installation capability for non-administrative accounts via RBAC, require multi-person approval for plugin installations (separate approval from the install action), and conduct manual security review of any plugin before installation proceeds. Document and audit all plugin installation events to detect patterns of warnings being ignored. Configure OpenClaw's scan settings to the strictest sensitivity level to maximize detection of suspicious indicators. These controls mitigate but do not eliminate risk, as a determined operator can still override warnings.