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

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

OpenClaw CVE-2026-43574

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

CVE-2026-43574 has a CVSS 4.0 base score of 6.0 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/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-27299 MEDIUM

Permissive List of Allowed Inputs (CWE-183)

2026-05-05 VulnCheck

Information Disclosure Openclaw

6.0

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

6.0 MEDIUM

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

None

Scope

Lifecycle Timeline

CVSS changed

May 05, 2026 - 12:37 NVD

6.5 (MEDIUM) 6.0 (MEDIUM)

Source Code Evidence Fetched

May 05, 2026 - 12:22 vuln.today

Analysis Generated

May 05, 2026 - 12:22 vuln.today

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.4.12.

DescriptionCVE.org

OpenClaw before 2026.4.12 contains an improper authorization vulnerability in helper-backed channels where empty resolved approver lists are interpreted as explicit approval authorization. Attackers can resolve pending approvals without proper authorization by exploiting this logic flaw if they know an approval id.

AnalysisAI

OpenClaw before version 2026.4.12 contains an improper authorization flaw in helper-backed channels where empty resolved approver lists are incorrectly interpreted as explicit approval authorization. Authenticated attackers who know an approval ID can resolve pending approvals without proper authorization by exploiting this logic error, bypassing intended sender authorization checks. This vulnerability has a CVSS score of 6.5 (medium) with network attack vector and requires only low privileges, though no public exploit code or active exploitation has been identified.

Technical ContextAI

OpenClaw is a Node.js package (npm ecosystem) that handles approval workflows in communication channels like Signal. The vulnerability exists in the approval authorization logic, specifically in the channel-approval-auth.ts and approval-auth-helpers.ts modules. The root cause (CWE-183: Permissive List of Allowed Inputs) stems from the system treating an empty approver list returned from the resolveApprovers() function as implicit approval authorization rather than requiring explicit approval from configured authorizers. The patch differentiates between implicit fallback authorization (when an empty approver list is returned) and explicit authorization (when actual approvers are configured), preventing unauthorized senders from exploiting the empty-list edge case. The fix adds a non-enumerable marker to track implicit vs. explicit approval states, ensuring that even when no specific approvers are resolved, the system still enforces sender authentication checks.

RemediationAI

Upgrade OpenClaw to version 2026.4.12 or later (recommend 2026.4.14 for latest stability). If immediate upgrade is not feasible, restrict network access to OpenClaw approval endpoints using firewall rules or WAF policies to limit the attack surface, though this does not address the underlying authorization logic. Additionally, audit approval logs in existing deployments to identify any potentially unauthorized approval resolutions made before patching. The patch (commit 0a105c0900de701d2ee9f1abc96b017afbd0afdd, PR #65714) refactors the authorization logic to mark empty-approver fallback states as implicit rather than explicit authorization, ensuring that sender authentication checks are not bypassed. No breaking changes are documented; the fix is a drop-in replacement with only test additions confirming the corrected behavior.