How severe is GHSA-r294-2894-92j3?

No CVSS score has been assigned to GHSA-r294-2894-92j3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r294-2894-92j3?

GHSA-r294-2894-92j3 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-r294-2894-92j3?

Update openclaw to 2026.2.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r294-2894-92j3 is resolved across your whole dependency graph.

How do I detect GHSA-r294-2894-92j3 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-r294-2894-92j3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-r294-2894-92j3?

O3 pinpoints whether GHSA-r294-2894-92j3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-r294-2894-92j3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r294-2894-92j3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-r294-2894-92j3 published, and has it been updated?

GHSA-r294-2894-92j3 was published on March 3, 2026 and was last updated on March 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-r294-2894-92j3

OpenClaw has stored XSS in exported session HTML viewer via markdown/raw-HTML rendering

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.3Mdownloads / week

Description

Summary

The exported session HTML viewer allowed stored XSS when untrusted session content included raw HTML markdown tokens or unescaped metadata fields.

Impact

Opening a crafted exported HTML session could execute attacker-controlled JavaScript in the viewer context. This can expose session content in the page and enable phishing or UI spoofing in the trusted export view.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.2.22-2
Patched version (released): >= 2026.2.23

Technical Details

The exporter rendered markdown with marked.parse(...) and inserted HTML via innerHTML, but did not override the html renderer token path. Raw HTML (for example <img ... onerror=...>) was passed through. Additional tree/header metadata fields were interpolated without escaping in the export template.

Reproduction

Create a session containing content like <img src=x onerror=alert(1)>.
Export the session to HTML.
Open the exported file.
Observe script execution from injected content.

Remediation

Added a marked html(token) renderer override that escapes raw HTML tokens.
Escaped previously unescaped tree/header metadata fields in the export template.
Added image MIME sanitization for exported data-URL image rendering.
Added regression tests for markdown/token and metadata escaping paths.

Fix Commit(s)

f8524ec77a3999d573e6c6b8a5055bf35c49a2e6

Release Process Note

patched_versions is pre-set to the released version (>= 2026.2.23). This advisory now reflects released fix version 2026.2.23.

OpenClaw thanks @allsmog for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.23

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r294-2894-92j3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-r294-2894-92j3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-r294-2894-92j3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary The exported session HTML viewer allowed stored XSS when untrusted session content included raw HTML markdown tokens or unescaped metadata fields. ## Impact Opening a crafted exported HTML session could execute attacker-controlled JavaScript in the viewer context. This can expose session content in the page and enable phishing or UI spoofing in the trusted export view. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `<= 2026.2.22-2` - Patched version (released): `>= 2026.2.23` ## Technical Details The exporter rendered markdown with `marked.pa

O3 Security · Impact-Aware SCA

Is GHSA-r294-2894-92j3 in your dependencies?

O3 detects GHSA-r294-2894-92j3 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works