CVE-2026-53841
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenClaw 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenClaw before version 2026.5.12 has a stored XSS vulnerability in its session HTML export feature. The exported HTML files preserve unsafe javascript: and data: URI schemes in links, allowing attackers to embed malicious links that execute arbitrary JavaScript when a trusted user opens the exported file and clicks the malicious link.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.5.12= 2026.5.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenClaw installation and versionLocate the OpenClaw application and determine its installed version (for example, check the application's 'About' section, its executable properties, or any version file in its installation directory)Affected if The installed version is earlier than 2026.5.12 or exactly 2026.5.12
-
Locate exported session HTML filesSearch for HTML files that were exported using OpenClaw's session export feature - these are typically stored in the application's data directory, user documents folder, or the same location where export operations save outputAffected if Any HTML files exist from session exports performed with affected versions
-
Inspect exported HTML for unsafe URI schemesOpen the exported HTML files in a text editor or use a command to search for 'javascript:' or 'data:' strings within anchor (<a>) tags or href attributesAffected if The exported HTML contains links with javascript: or data: URI schemes in href attributes
A user is affected if they have OpenClaw version 2026.5.12 or earlier AND have exported session files that contain javascript: or data: URI schemes in links.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.5.12
Upgrade to OpenClaw version 2026.5.12 or later, which implements proper sanitization of links in exported HTML to remove unsafe URI schemes. Until upgraded, users should avoid clicking untrusted links in exported session files.
OpenClaw 2026.5.12 or later
- 1. Identify the current OpenClaw version installed by checking the application or configuration files
- 2. Download the fixed release (2026.5.12 or later) from the official OpenClaw repository or distribution channel
- 3. Before applying the upgrade, backup all existing configurations, exported session files, and data to prevent data loss
- 4. Install the upgraded version following the standard installation procedure for your deployment method
- 5. After upgrading, verify that exported HTML session files properly sanitize javascript: and data: URL schemes
- 6. Test a sample exported HTML file to confirm the XSS vulnerability is remediated by attempting to inject javascript: or data: links and confirming they are neutralized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53841 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53841 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data