OpenClaw versions before 2026.8.1 fail to validate all source fields in structured message attachments, allowing attackers to hide unvalidated host… (CVE-2026-100536)
OpenClaw versions prior to 2026.8.1 have a vulnerability where not all source fields in structured message attachments are validated. This allows attackers to bypass sandbox path validation by hiding unvalidated host paths behind allowed attachment sources. Exploitation can cause Telegram delivery to read and send files from the host system that should normally be rejected.
AI Analysis
Technical Summary
The vulnerability in OpenClaw before version 2026.8.1 involves incomplete validation of source fields in structured message attachments. Attackers can supply multiple source fields to circumvent sandbox path validation mechanisms, enabling the Telegram delivery component to access and transmit known host files that would otherwise be blocked. This issue is tracked as CVE-2026-100536 and is associated with CWE-22 (Improper Limitation of a Pathname to a Restricted Directory).
Potential Impact
Successful exploitation allows an attacker with low privileges to cause Telegram delivery to read and send sensitive files from the host system, potentially leading to unauthorized disclosure of confidential information. The CVSS score is 6.5 (High), reflecting network attack vector, low attack complexity, required privileges, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact.
Mitigation Recommendations
A fix is available in OpenClaw version 2026.8.1. Users should upgrade to this version or later to address the vulnerability. No other mitigation guidance is provided or necessary as the issue is resolved by the official patch.
OpenClaw versions before 2026.8.1 fail to validate all source fields in structured message attachments, allowing attackers to hide unvalidated host… (CVE-2026-100536)
Description
OpenClaw versions prior to 2026.8.1 have a vulnerability where not all source fields in structured message attachments are validated. This allows attackers to bypass sandbox path validation by hiding unvalidated host paths behind allowed attachment sources. Exploitation can cause Telegram delivery to read and send files from the host system that should normally be rejected.
CVSS v3.1
Score 6.5medium
Affected software
pkg:github/openclaw/openclawRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in OpenClaw before version 2026.8.1 involves incomplete validation of source fields in structured message attachments. Attackers can supply multiple source fields to circumvent sandbox path validation mechanisms, enabling the Telegram delivery component to access and transmit known host files that would otherwise be blocked. This issue is tracked as CVE-2026-100536 and is associated with CWE-22 (Improper Limitation of a Pathname to a Restricted Directory).
Potential Impact
Successful exploitation allows an attacker with low privileges to cause Telegram delivery to read and send sensitive files from the host system, potentially leading to unauthorized disclosure of confidential information. The CVSS score is 6.5 (High), reflecting network attack vector, low attack complexity, required privileges, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact.
Mitigation Recommendations
A fix is available in OpenClaw version 2026.8.1. Users should upgrade to this version or later to address the vulnerability. No other mitigation guidance is provided or necessary as the issue is resolved by the official patch.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-xwq7-8jj4-2g7j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-100536"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6ab74f2cf7a7c54106e13840
Added to database: 09/26/2026, 04:50:52 UTC
Last enriched: 09/26/2026, 04:55:56 UTC
Last updated: 09/27/2026, 01:47:40 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.