Disclosed weakness · no CVE recorded

OpenClaw could export secrets in multiline telemetry content

OpenClaw · OpenClaw · OpenTelemetry model and tool content capture

First documented disclosure · Review checkpoint

Summary

With optional content capture enabled, model or tool text could reach an OpenTelemetry destination with sensitive assignments still visible.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The maintainer records a correction. The reviewed sources identify no malicious exploitation.

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

Encoding structured content as JSON before redacting multiline strings could obscure line boundaries needed to recognize the sensitive text.

Conditions required

An operator enables OpenTelemetry content capture and a recorded model or tool field includes matching sensitive text after a line break.

Potential impact

People or systems with access to the exported telemetry could read values that should have been masked.

Affected versions and configurations

The maintainer confirmed the problem on its development baseline and did not publish a complete affected release range.

Fix and mitigation status

The correction is listed in stable release 2026.11.4 and was also documented in prerelease 2026.11.5-beta.3.

Practical next steps

Use a build containing the correction or disable content capture. Review the telemetry destination, retention period and any credentials present in earlier exports.

Operating lesson

Redact individual strings before encoding them for export and verify the output at the telemetry destination.

Evidence and limits

This affects an opt-in OpenTelemetry export path. The earlier October corrections cover operational logs in separate integrations.

Sources