Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Path Traversal Arbitrary File Read in OpenClaw browser upload action

IdentifiersCVE-2026-26329CWE-22· Improper Limitation of a Pathname…

CVE-2026-26329 affects OpenClaw prior to version 2026.2.14. The vulnerability is in the Gateway-exposed browser tool upload action, where attacker-supplied file paths were passed to Playwright's setInputFiles() API without being restricted to a safe upload root. Because absolute paths and path traversal sequences were accepted, an authenticated attacker could cause the Gateway host to access arbitrary local files outside the intended uploads directory. The issue is effectively a path traversal / improper pathname restriction flaw in the browser control hook path handling. The vendor states that version 2026.2.14 fixes this by confining upload paths to OpenClaw's temp uploads root (DEFAULT_UPLOAD_DIR) and rejecting traversal or escape paths.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary local file read from the OpenClaw Gateway host, resulting in high confidentiality impact. Exposed files may include application data, configuration files, tokens, credentials, or other sensitive host-resident material accessible to the Gateway process. The advisory notes that exfiltration may occur through page JavaScript such as FileReader, or via agent/browser snapshots and related browser automation flows. If the Gateway is exposed beyond loopback through LAN binding, tailnet exposure, reverse proxies, or tunnels, the practical attack surface and risk increase accordingly.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, keep the Gateway bound to loopback only and avoid exposing it through LAN binds, tailnets, reverse proxies, or tunnels. Restrict or disable the browser tool through tool policy where it is not operationally required. Limit issuance and retention of valid Gateway credentials, including bearer tokens and passwords. Monitor for suspicious requests to POST /tools/invoke using tool=browser and action=upload, and to POST /hooks/file-chooser containing unexpected absolute paths or traversal sequences.

Remediation

Patch, then assume compromise.

Upgrade OpenClaw / the openclaw package to version 2026.2.14 or later. The fix confines upload paths to DEFAULT_UPLOAD_DIR and rejects traversal and escape paths before invoking Playwright setInputFiles(). The referenced fix commit is 3aa94afcfd12104c683c9cad81faf434d0dadf87.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenclawOpenclawapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.