The OpenClaw npm package prior to version 2026.8.1 has a vulnerability where third-party provider credentials can be sent to the wrong endpoint. Specifically, when a third-party provider uses an OpenAI-compatible API and the model metadata lacks a concrete base URL, a pinned session that persists after a model configuration hot reload retains the provider's credentials while the OpenAI SDK defaults to its own endpoint. This mismatch causes requests to disclose credentials to unrelated provider endpoints and results in misleading authentication errors. The vulnerability is addressed in version 2026.8.1.

The vulnerability can lead to the unintended disclosure of third-party provider credentials to unrelated endpoints, potentially exposing sensitive authentication information. This may cause authentication failures and could require credential rotation by affected operators. There is no indication of direct data compromise or system takeover, but the confidentiality of credentials is impacted.

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.