Summary
Workspace provider auth choices could auto-enable untrusted provider plugins.
Affected Packages / Versions
- Package:
openclaw - Ecosystem: npm
- Affected versions:
< 2026.4.9 - Patched versions:
>= 2026.4.9
Technical Details
The fix prefers trusted provider origins for auth choices and excludes untrusted workspace choices unless they are explicitly enabled.
Fix Commit(s)
2d97eae53e212ae26f3aebcd6a50ffc6877f770d- PR: #62368
Release Process Note
Users should upgrade to openclaw 2026.4.9 or newer. The latest npm release, 2026.4.14, already includes the fix.
Credits
Thanks to @zpbrent for reporting this issue.
Impact
Non-interactive onboarding could select a provider auth choice shadowed by an untrusted workspace plugin, auto-enabling that plugin during auth setup.
CVE-2026-43569 has a CVSS score of 8.8 (High). The vector is network-reachable, no privileges required, and user interaction required. 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.9); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
The issue was fixed in #62368. The first stable tag containing the fix is v2026.4.9, and [email protected] includes the fix.
Frequently Asked Questions
- What is CVE-2026-43569? CVE-2026-43569 is a high-severity security vulnerability in openclaw (npm), affecting versions < 2026.4.9. It is fixed in 2026.4.9.
- How severe is CVE-2026-43569? CVE-2026-43569 has a CVSS score of 8.8 (High). 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.
- Which versions of openclaw are affected by CVE-2026-43569? openclaw (npm) versions < 2026.4.9 is affected.
- Is there a fix for CVE-2026-43569? Yes. CVE-2026-43569 is fixed in 2026.4.9. Upgrade to this version or later.
- Is CVE-2026-43569 exploitable, and should I be worried? Whether CVE-2026-43569 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
- What actually determines whether CVE-2026-43569 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.
- How do I fix CVE-2026-43569? Upgrade
openclawto 2026.4.9 or later.