Disclosed weakness · no CVE recorded

OpenClaw could restore a plaintext credential alongside a managed secret reference

OpenClaw · OpenClaw · Doctor repair

First documented disclosure · Review checkpoint

Summary

Configuration repair could import a stale provider key from a generated model catalog when the stored setting already referenced a managed secret.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The upstream sources document the behavior and correction. They identify no malicious use.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The repair process did not recognize the existing reference as the authoritative credential.

Conditions required

An operator runs configuration repair with both a managed reference and an older plaintext catalog entry.

Potential impact

A stale credential could be copied back into persistent configuration.

Affected versions and configurations

The upstream report identifies the affected behavior without specifying a complete version range.

Fix and mitigation status

The 2026.11.4 stable release includes this issue-specific correction.

Practical next steps

Deploy the correction, inspect repaired configuration for duplicate secrets and rotate an exposed key.

Operating lesson

Include maintenance and repair utilities in secret-storage policy.

Evidence and limits

The source establishes a local persistence risk. It does not report transfer to a third party.

Sources