CVE-2026-100548

OpenClaw before 2026.8.1 Credential Exposure via Embedding Fallback

Published Sep 26, 2026 CVSS 4.0 · 6 Medium EPSS < 1% KEV · Not listed
Description
OpenClaw (npm package 'openclaw') versions >= 2026.3.28 and < 2026.8.1 contain a credential exposure issue in memory embedding failover. When remote embedding fallback is configured and the primary embedding provider fails, the request can be sent to a different fallback provider while still reusing the primary provider's configured API key, causing that credential to be transmitted as a bearer token to an unintended vendor. The practical impact depends on the configured providers, whether failover occurs, and the privileges attached to the primary provider key. The issue is fixed in 2026.8.1; as a workaround, disable cross-provider embedding fallback or configure each provider with separate, narrowly scoped credentials.

Analysis

AI-generated

Technical impact

The vulnerability lies in OpenClaw's embedding fail‑over logic, where a request that falls back to a secondary provider still carries the primary provider's API key as a bearer token. This credential exposure flaw (CWE-200) exposes the key to an unintended vendor, allowing an attacker who can force or observe the fail‑over to obtain the key and potentially access protected resources or data. The actual damage depends on the provider configuration, the likelihood of fail‑over, and the permission level of the exposed key.

Affected Systems

OpenClaw, the npm package named openclaw, for all releases starting at 2026.3.28 up to but excluding 2026.8.1. These versions are affected by the credential exposure flaw in the memory embedding failover pathway.

Risk and Exploitability

The flaw carries a CVSS score of 6.0, indicating moderate severity. No EPSS information is available, and the issue is not listed in the CISA KEV catalog. The exploit requires the application to be misconfigured with cross‑provider embedding fallback enabled, and an attacker must trigger a provider failure or otherwise force the fail‑over path. Once the fallback request is sent, the primary API key travels to the unintended vendor, creating a direct credential disclosure risk. Although the conditions for exploitation are non‑trivial, remediation is straightforward and the potential impact on credential confidentiality is significant.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor‑issued update to OpenClaw version 2026.8.1 or later.
  • If an update is not immediately feasible, disable cross‑provider embedding fallback in the configuration.
  • Configure each embedding provider with a unique, narrowly scoped API key so that fail‑over requests do not reuse the primary key.
  • Regularly review provider credentials to ensure they have least privilege and are not shared between providers.

Generated by OpenCVE AI on September 26, 2026 at 04:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description OpenClaw (npm package 'openclaw') versions >= 2026.3.28 and < 2026.8.1 contain a credential exposure issue in memory embedding failover. When remote embedding fallback is configured and the primary embedding provider fails, the request can be sent to a different fallback provider while still reusing the primary provider's configured API key, causing that credential to be transmitted as a bearer token to an unintended vendor. The practical impact depends on the configured providers, whether failover occurs, and the privileges attached to the primary provider key. The issue is fixed in 2026.8.1; as a workaround, disable cross-provider embedding fallback or configure each provider with separate, narrowly scoped credentials.
Title OpenClaw before 2026.8.1 Credential Exposure via Embedding Fallback
First Time appeared Openclaw
Openclaw openclaw
Weaknesses CWE-200
CPEs cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*
Vendors & Products Openclaw
Openclaw openclaw
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 6, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 30, 2026, 12:22 AM
Reserved
Sep 26, 2026, 1:02 AM
Status
Deferred
Published
Sep 26, 2026, 3:17 AM
Modified
Sep 30, 2026, 1:16 AM