CVE-2026-100536 OpenClaw CVE debrief

Who should care

Defenders responsible for OpenClaw deployments should assess exposure and prioritize verification and remediation. This includes reviewing and validating source fields in structured message attachments, monitoring for potential path traversal attacks, and verifying OpenClaw versions. Additionally, defenders should review compensating controls for exposed systems and track exceptions and retest remediated assets.

Why it matters

CVE-2026-100536 is a path traversal vulnerability in OpenClaw versions before 2026.8.1. Defenders should prioritize verification and remediation to prevent potential attacks.

• Path traversal attacks may occur if OpenClaw versions before 2026.8.1 are not updated
• Defenders must verify OpenClaw versions and validate source fields in structured message attachments

Technical summary

OpenClaw versions before 2026.8.1 fail to validate all source fields in structured message attachments, allowing attackers to hide unvalidated host paths behind allowed attachment sources. This vulnerability can lead to path traversal attacks if not addressed. Defenders should prioritize verification and remediation to prevent potential attacks. The vulnerability can be exploited by providing multiple source fields to bypass sandbox path validation and cause Telegram delivery to read and send known host files that would otherwise be rejected.

Defensive priority

Defenders should prioritize verifying OpenClaw versions and updating to 2026.8.1 or later to prevent path traversal attacks.

Recommended defensive actions

• Verify OpenClaw versions and update to 2026.8.1 or later
• Review and validate source fields in structured message attachments
• Monitor for potential path traversal attacks
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. Further verification is required to determine the full scope of affected versions and potential impacts. Defenders should verify OpenClaw versions and validate source fields in structured message attachments. The vulnerability can be exploited by providing multiple source fields to bypass sandbox path validation and cause Telegram delivery to read and send known host files that would otherwise be rejected.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.