openclaw
Affected
- introduced
0, fixed2026.2.14(semver)
Fixed versions
2026.2.14
Fix
- Fixed version
2026.2.14npm install [email protected]
Advisory
Also known as: CVE-2026-26329
OpenClaw has a path traversal in browser upload allows local file read
Summary
Authenticated attackers can read arbitrary files from the Gateway host by supplying absolute paths or path traversal sequences to the browser tool's upload action. The server passed these paths to Playwright's setInputFiles() APIs without restricting them to a safe root.
Severity remains High due to the impact (arbitrary local file read on the Gateway host), even though exploitation requires authenticated access.
Exploitability / Preconditions
This is not a "drive-by" issue.
An attacker must:
browser tool permitted by tool policy for the target session/context (and have browser support enabled).If an operator exposes the Gateway beyond loopback (LAN/tailnet/custom bind, reverse proxy, tunnels, etc.), the impact increases accordingly.
Affected Packages / Versions
openclaw (npm)< 2026.2.14 (includes latest published 2026.2.13)>= 2026.2.14 (planned next release)Details
Entry points:
POST /tools/invoke with {"tool":"browser","action":"upload",...}POST /hooks/file-chooser (browser control hook)When the upload paths are not validated, Playwright reads the referenced files from the local filesystem and attaches them to a page-level <input type="file">. Contents can then be exfiltrated by page JavaScript (e.g. via FileReader) or via agent/browser snapshots.
Impact: arbitrary local file read on the Gateway host (confidentiality impact).
Fix
Upload paths are now confined to OpenClaw's temp uploads root (DEFAULT_UPLOAD_DIR) and traversal/escape paths are rejected.
This fix was implemented internally; the reporter provided a clear reproduction and impact analysis.
Fix commit(s):
Thanks @p80n-sec for reporting.
High Basis: The source's own band: HIGH
0, fixed 2026.2.14 (semver)2026.2.14
2026.2.14npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0