CVE-2026-43574

Empty approver lists could grant explicit approval authorization.

Affected Packages / Versions

• Package: openclaw
• Ecosystem: npm
• Affected versions: < 2026.4.12
• Patched versions: >= 2026.4.12

Technical Details

The fix prevents empty approver lists from granting explicit approval authorization and adds regression coverage for unauthorized senders.

Fix Commit(s)

• 0a105c0900de701d2ee9f1abc96b017afbd0afdd
• PR: #65714

Release Process Note

Users should upgrade to openclaw 2026.4.12 or newer. The latest npm release, 2026.4.14, already includes the fix.

Credits

Thanks to @anshumanbh for reporting this issue.

For helper-backed channels, an empty resolved approver list could be interpreted as explicit approval authorization, allowing a sender outside the normal channel authorization gate to resolve pending approvals if they knew an approval id.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-43574 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.4.12); upgrading removes the vulnerable code path.

Kodem intelligence

The issue was fixed in #65714. The first stable tag containing the fix is v2026.4.12, and [email protected] includes the fix.

1. What is CVE-2026-43574? CVE-2026-43574 is a medium-severity missing authorization vulnerability in openclaw (npm), affecting versions < 2026.4.12. It is fixed in 2026.4.12. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-43574? CVE-2026-43574 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-43574? openclaw (npm) versions < 2026.4.12 is affected.
4. Is there a fix for CVE-2026-43574? Yes. CVE-2026-43574 is fixed in 2026.4.12. Upgrade to this version or later.
5. Is CVE-2026-43574 exploitable, and should I be worried? Whether CVE-2026-43574 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-43574 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-43574? Upgrade openclaw to 2026.4.12 or later.