OpenClaw (npm package 'openclaw') versions >= 2026.3.28 and < 2026.8.1 contain a credential exposure issue in memory embedding failover. (CVE-2026-100548)
OpenClaw npm package versions from 2026.3.28 up to but not including 2026.8.1 have a credential exposure vulnerability in the memory embedding failover mechanism. When the primary embedding provider fails and a remote fallback is used, the API key of the primary provider can be sent to an unintended fallback provider as a bearer token. This exposure depends on the configured providers, failover occurrence, and privileges of the primary API key. The issue is resolved in version 2026.8.1. Workarounds include disabling cross-provider embedding fallback or using separate, narrowly scoped credentials per provider.
AI Analysis
Technical Summary
The OpenClaw npm package (versions >= 2026.3.28 and < 2026.8.1) contains a vulnerability where, during embedding failover, the primary provider's API key is reused and transmitted to a fallback provider unintentionally. This leads to credential exposure as the API key is sent as a bearer token to a vendor not originally intended to receive it. The vulnerability arises only if remote embedding fallback is configured and triggered. The fix is included in version 2026.8.1. Until then, disabling cross-provider fallback or segregating credentials per provider can mitigate the risk.
Potential Impact
The vulnerability can lead to unauthorized disclosure of the primary embedding provider's API key to unintended fallback providers. The severity of impact depends on the privileges associated with the exposed API key and the fallback configuration. There is no indication of integrity or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix is available in OpenClaw version 2026.8.1. Users should upgrade to this version to fully remediate the issue. As a workaround before upgrading, disable cross-provider embedding fallback or configure each embedding provider with separate, narrowly scoped credentials to prevent credential exposure.
OpenClaw (npm package 'openclaw') versions >= 2026.3.28 and < 2026.8.1 contain a credential exposure issue in memory embedding failover. (CVE-2026-100548)
Description
OpenClaw npm package versions from 2026.3.28 up to but not including 2026.8.1 have a credential exposure vulnerability in the memory embedding failover mechanism. When the primary embedding provider fails and a remote fallback is used, the API key of the primary provider can be sent to an unintended fallback provider as a bearer token. This exposure depends on the configured providers, failover occurrence, and privileges of the primary API key. The issue is resolved in version 2026.8.1. Workarounds include disabling cross-provider embedding fallback or using separate, narrowly scoped credentials per provider.
CVSS v3.1
Score 5.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The OpenClaw npm package (versions >= 2026.3.28 and < 2026.8.1) contains a vulnerability where, during embedding failover, the primary provider's API key is reused and transmitted to a fallback provider unintentionally. This leads to credential exposure as the API key is sent as a bearer token to a vendor not originally intended to receive it. The vulnerability arises only if remote embedding fallback is configured and triggered. The fix is included in version 2026.8.1. Until then, disabling cross-provider fallback or segregating credentials per provider can mitigate the risk.
Potential Impact
The vulnerability can lead to unauthorized disclosure of the primary embedding provider's API key to unintended fallback providers. The severity of impact depends on the privileges associated with the exposed API key and the fallback configuration. There is no indication of integrity or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix is available in OpenClaw version 2026.8.1. Users should upgrade to this version to fully remediate the issue. As a workaround before upgrading, disable cross-provider embedding fallback or configure each embedding provider with separate, narrowly scoped credentials to prevent credential exposure.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9ffh-hv34-6589
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-100548"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6ab74f2df7a7c54106e1384e
Added to database: 09/26/2026, 04:50:53 UTC
Last enriched: 09/26/2026, 04:56:32 UTC
Last updated: 09/26/2026, 06:07:40 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.