Summary
OpenClaw skills.status could leak secrets to operator.read clients
skills.status could disclose secrets to operator.read clients by returning raw resolved config values in configChecks for skill requires.config paths.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
<= 2026.2.13 - Patched:
2026.2.14
Details
The gateway method skills.status returned a requirements report that included configChecks[].value (the resolved value for each requires.config entry). If a skill required a broad config subtree (for example channels.discord), the report could include secrets such as Discord bot tokens.
skills.status is callable with operator.read, so read-scoped clients could obtain secrets without operator.admin / config.* access.
Mitigation
Rotate any Discord tokens that may have been exposed to read-scoped clients.
Thanks @simecek for reporting.
Fix commits d3428053d95eefbe10ecf04f92218ffcba55ae5a and ebc68861a61067fc37f9298bded3eec9de0ba783 confirmed on main and in v2026.2.14. Upgrade to openclaw >= 2026.2.14.
Impact
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- Stop including raw resolved config values in requirement checks (return only
{ path, satisfied }). - Narrow the Discord skill requirement to the token key.
Fix commit(s):
- d3428053d95eefbe10ecf04f92218ffcba55ae5a
- ebc68861a61067fc37f9298bded3eec9de0ba783
Frequently Asked Questions
- What is CVE-2026-26326? CVE-2026-26326 is a medium-severity security vulnerability in openclaw (npm), affecting versions < 2026.2.14. It is fixed in 2026.2.14.
- Which versions of openclaw are affected by CVE-2026-26326? openclaw (npm) versions < 2026.2.14 is affected.
- Is there a fix for CVE-2026-26326? Yes. CVE-2026-26326 is fixed in 2026.2.14. Upgrade to this version or later.
- Is CVE-2026-26326 exploitable, and should I be worried? Whether CVE-2026-26326 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-26326 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-26326? Upgrade
openclawto 2026.2.14 or later.