Cyber Resilience

CVE-2026-43574

Openclaw ≤ 2026.4.12

Public PoC
Published
05 May 2026
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v4 6.0
Click a component to see what it means
Raw vectorCVSS: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 Score 0.0024 15th percentile
Risk Priority 33 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-43574 is a medium-severity Permissive List of Allowed Inputs (CWE-183) vulnerability in Openclaw Openclaw. Its CVSS base score is 6.0 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

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…

more

id.

CWE(s)
CWE-183

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-44111Same product: Openclaw Openclaw
CVE-2026-35649Same product: Openclaw Openclaw
CVE-2026-41387Same product: Openclaw Openclaw
CVE-2026-22175Same product: Openclaw Openclaw
CVE-2026-28477Same product: Openclaw Openclaw
CVE-2026-44996Same product: Openclaw Openclaw
CVE-2026-28393Same product: Openclaw Openclaw
CVE-2026-41347Same product: Openclaw Openclaw
CVE-2026-28363Same product: Openclaw Openclaw
CVE-2026-32007Same product: Openclaw Openclaw

Affected Assets

openclaw
openclaw
≤ 2026.4.12

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V4.4.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Strict validity checks on inputs directly stop overly permissive allow lists from being used as the protection mechanism.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require rigorous allow-list design and testing that prevents permissive input validation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect overly broad allow-lists, but does not inherently prevent their creation.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate strict, minimal allow-lists and input validation rules that prevent overly permissive lists.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require explicit, least-privilege input validation designs that directly address permissive allow-lists.

A.8.28 Secure coding partial match
prevents

Secure coding standards enforce rigorous input validation and reject unsafe values, mitigating permissive allow-list weaknesses.

References