Disclosed weakness · no CVE recorded
OpenClaw left identifying phone numbers in sanitized support archives
OpenClaw · OpenClaw · diagnostic export
First documented disclosure · Review checkpoint
Summary
A diagnostic export labeled as sanitized could retain telephone identifiers in configuration keys.
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.
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
Redaction handled values differently from identifying field names.
Conditions required
An operator generates and shares a triage archive containing affected configuration.
Potential impact
A support recipient could receive a private identifier.
Affected versions and configurations
The reporter confirmed the behavior in OpenClaw 2026.9.9. A complete affected range was not published.
Fix and mitigation status
The 2026.11.4 stable release includes this issue-specific correction.
Practical next steps
Deploy the fix and review previously shared diagnostic bundles for personal identifiers.
Operating lesson
Include keys and values when validating redaction of exported data.
Evidence and limits
A generated archive was checked directly. The report did not establish a third-party disclosure.
Sources
- OpenClaw · triage diagnostics leaks phone-number map keys in config/sanitized.json
Primary source ·
- OpenClaw · fix: redact identifying map keys in triage archives
Primary source ·
- OpenClaw 2026.11.4 stable release notes
Primary source ·