Is there a patch available for CVE-2026-53841?

Yes, a patch is available for CVE-2026-53841. Update the affected software to the latest version immediately.

OpenClaw CVE-2026-53841

Q: What is the CVSS score of CVE-2026-53841?

CVE-2026-53841 has a CVSS 4.0 base score of 2.1 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-37143 LOW

Improper Neutralization of Script in Attributes in a Web Page (CWE-83)

2026-06-16 VulnCheck

GHSA-6xcg-6q43-rj2v

GHSA-w9hf-3pp7-pvxv

XSS Openclaw

2.1

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

2.1 LOW

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

4.7 MEDIUM

AC:H maps to CVSS 4.0 AT:P (attacker must control session content); UI:R for required link-click; S:C for browser-context scope change.

3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

4.0 AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Scope

Lifecycle Timeline

Patch available

Jun 16, 2026 - 20:02 EUVD

Analysis Generated

Jun 16, 2026 - 19:07 vuln.today

DescriptionCVE.org

OpenClaw before 2026.5.12 contains a cross-site scripting vulnerability in exported session HTML that preserves unsafe javascript: and data: links in generated content. Attackers can execute browser-side scripts if a trusted operator opens the exported file and activates a malicious link.

AnalysisAI

Stored cross-site scripting in OpenClaw's session HTML export feature allows unsafe javascript: and data: URI schemes to survive into generated output files. All OpenClaw versions before 2026.5.12 are affected; exploitation requires a trusted operator to open an exported session HTML file and actively click a crafted link, at which point arbitrary JavaScript executes in their browser context. No public exploit has been identified at time of analysis and no CISA KEV listing exists; the CVSS 4.0 score of 2.1 reflects the narrow attack prerequisites and limited subsequent-system impact.

Technical ContextAI

OpenClaw (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) produces exportable HTML documents from session content. The root cause is CWE-83 (Improper Neutralization of Script in Attributes in a Web Page): the HTML export renderer does not sanitize javascript: and data: URI schemes from link attributes before writing them to the output file. These URI schemes are natively executable by browsers - a browser that renders an anchor with href='javascript:...' or href='data:text/html,...' will execute the payload when the user clicks the link. Proper remediation requires stripping or encoding these schemes during export, as they have no legitimate use in generated static HTML sessions.

RemediationAI

Upgrade OpenClaw to version 2026.5.12 or later, which addresses the unsafe link-scheme handling in the session HTML export renderer; consult the vendor advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-w9hf-3pp7-pvxv for patch details. If an immediate upgrade is not feasible, operators should avoid opening exported HTML files directly in a standard browser tab; instead, review session content within the OpenClaw application UI before exporting. As a compensating control, exported HTML files can be opened in a sandboxed browser profile or a browser with JavaScript execution disabled - note that disabling JavaScript eliminates the attack vector but may also break any legitimate interactivity in the exported document. Additionally, access controls should be applied to restrict who can contribute content to sessions reviewed by privileged operators, reducing the attacker's ability to inject malicious links.