CVE-2026-100528: OpenClaw (npm package 'openclaw') before 2026.8.1 could send third-party provider credentials to the
Affects openclawSource GCVE Database
Not known to be exploited · CVSS 5.4 Medium : upgrade to 2026.8.1 when convenient.
Data as of 9 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.8.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 26 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade openclaw to 2026.8.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmopenclawpkg:npm/openclawOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade OpenClaw to version 2026.8.1 or later, where this issue is fixed. Operators who have observed this condition should rotate the affected third-party provider credentials to prevent misuse. No other mitigation steps are indicated.
Description
OpenClaw (npm package 'openclaw') before 2026.8.1 could send third-party provider credentials to the wrong endpoint. In affected versions, when a third-party provider uses an OpenAI-compatible API and the resolved model metadata lacks a concrete base URL, a pinned session that continues after a model configuration hot reload retains that provider's credential while the OpenAI SDK selects its own default endpoint. A resulting request could disclose the configured third-party provider credential to an unrelated provider endpoint and fail with a misleading authentication error. Operators who observed this condition should rotate the affected credential. The issue is fixed in 2026.8.1.