CVE-2026-53841: OpenClaw Cross-Site Scripting (XSS) in Session Export

Technical summary

The vulnerability is a stored/reflected XSS issue (CWE-83: Improper Neutralization of Script-Related HTML Tags) occurring at the point of HTML export in OpenClaw. When session data is exported, the application fails to neutralize or strip javascript: protocol handlers and data: URIs in generated HTML content. These unsafe links remain embedded in the exported file. When a trusted operator later opens the HTML file and clicks on or otherwise activates such a link, the browser executes the embedded script with the privileges of the operator's current security context. The CVSS 3.1 score of 6.1 (MEDIUM) reflects network accessibility, low attack complexity, no privileges required for exploitation, but user interaction as a prerequisite and limited impact scope (confidentiality and integrity, no availability impact).

Business impact

Operators who export and share session files risk exposing their browser sessions to script injection attacks. An attacker with the ability to influence exported content (or intercept and modify it in transit) can steal session tokens, harvest operator credentials, perform unauthorized actions within OpenClaw or connected systems, or redirect operators to malicious sites. For organizations using OpenClaw for security operations or sensitive data handling, a compromised operator session could provide lateral movement opportunities or enable further attacks on downstream systems.

Affected systems

OpenClaw versions before 2026.5.12 are affected. All documented instances in the advisory reference the same product line. Organizations running OpenClaw should verify their deployed version against 2026.5.12 and treat any earlier version as vulnerable.

Exploitability

Exploitability requires an attacker to either (1) directly control or inject malicious content into a session that an operator then exports, or (2) intercept and modify an exported HTML file before the operator opens it. The attack requires user interaction—the operator must open the exported file and activate the malicious link. No special network position or authentication is needed to craft the initial attack payload. This makes it suitable for targeted spear-phishing or supply-chain scenarios where attackers can influence exported content or trick operators into opening untrusted files.

Remediation

Upgrade OpenClaw to version 2026.5.12 or later. This version implements proper sanitization of javascript: and data: URIs in exported HTML, preventing them from being executed. Until patching is feasible, operators should avoid opening exported session files from untrusted sources and exercise caution when clicking links within any exported content. Organizations may also consider implementing additional controls such as sandboxed file inspection or disabling the export feature if it is not operationally necessary.

Patch guidance

Verify your OpenClaw deployment version and upgrade to 2026.5.12 or the latest available release. Consult the OpenClaw vendor advisory or release notes to confirm patch availability for your specific deployment model (on-premises, cloud, etc.). Testing the patch in a non-production environment is recommended before rolling out to production operators, as session export functionality may be integral to operational workflows. Once upgraded, existing exported files should be considered potentially unsafe and regenerated if they will be shared or archived long-term.

Detection guidance

Monitor for exports of OpenClaw session files, particularly those shared across organizational boundaries or stored in accessible repositories. Review exported HTML files for the presence of javascript: or data: URI schemes using grep or automated scanning. In production logs, look for multiple export operations from a single operator session in a short timeframe, which may indicate testing of a malicious export workflow. Network-level monitoring can flag suspicious file transfers of session exports to external recipients. Endpoint monitoring on operator machines can detect opening of suspicious HTML files followed by unexpected script execution.

Why prioritize this

This vulnerability ranks as MEDIUM severity (CVSS 6.1) and does not yet appear in CISA's Known Exploited Vulnerabilities (KEV) catalog. However, it affects a security-sensitive function (session export) used by operators. Organizations should prioritize patching based on internal usage of the export feature and the likelihood of operators encountering untrusted or attacker-influenced exported files. If OpenClaw is used in high-touch security operations or analyst workflows, prioritize patching more aggressively.

Risk score, explained

The CVSS 3.1 score of 6.1 reflects: (1) Network-accessible attack surface (AV:N), (2) low attack complexity with no special conditions required (AC:L), (3) no privileges needed to trigger the vulnerability (PR:N), (4) user interaction required (UI:R)—a critical limiting factor, (5) scope change (S:C) because the impact extends beyond the immediate security scope of OpenClaw, and (6) limited impact to confidentiality and integrity (C:L, I:L) with no availability impact (A:N). The presence of UI:R prevents a higher score, as reliable exploitation requires an operator to actively engage with the malicious link.

Frequently asked questions