CVE-2026-26326
Received Received - Intake
Information Disclosure in OpenClaw Skills.status Exposes Secrets

Publication date: 2026-02-19

Last updated on: 2026-02-23

Assigner: GitHub, Inc.

Description
OpenClaw is a personal AI assistant. Prior to version 2026.2.14, `skills.status` could disclose secrets to `operator.read` clients by returning raw resolved config values in `configChecks` for skill `requires.config` paths. Version 2026.2.14 stops including raw resolved config values in requirement checks (return only `{ path, satisfied }`) and narrows the Discord skill requirement to the token key. In addition to upgrading, users should rotate any Discord tokens that may have been exposed to read-scoped clients.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-19
Last Modified
2026-02-23
Generated
2026-05-06
AI Q&A
2026-02-20
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
openclaw openclaw to 2026.2.14 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The vulnerability in OpenClaw, a personal AI assistant, involves the `skills.status` feature prior to version 2026.2.14. It could inadvertently disclose secret information to clients with `operator.read` permissions by returning raw resolved configuration values in `configChecks` for skill requirements that need configuration (`requires.config`). This means sensitive data could be exposed to unauthorized users.

The issue was fixed in version 2026.2.14 by stopping the inclusion of raw resolved config values in requirement checks, instead returning only the path and whether the requirement is satisfied. Additionally, the Discord skill requirement was narrowed to only expose the token key.


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized disclosure of secret or sensitive configuration data to clients who only have read access (`operator.read`). Such exposure could compromise security by leaking tokens or other confidential information, potentially allowing attackers to misuse these secrets.

Users who may have had Discord tokens exposed should rotate those tokens to prevent misuse.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, you should upgrade OpenClaw to version 2026.2.14 or later.

Additionally, rotate any Discord tokens that may have been exposed to read-scoped clients to prevent unauthorized access.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart