CVE-2026-35668 — openclaw
CVE-2026-35668 is a Path Traversal vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
OpenClaw < 2026.3.24 - Sandbox Media Root Bypass via Unnormalized mediaUrl and fileUrl Parameters
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-35668.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
openclawnpmDescription
Fixed in OpenClaw 2026.3.24, the current shipping release.
Advisory Details
Title: Sandbox Media Root Bypass via Unnormalized mediaUrl / fileUrl Parameter Keys (CWE-22)
Description:
Summary
A path traversal vulnerability in the agent sandbox enforcement allows a sandboxed agent to read arbitrary files from other agents' workspaces by using the mediaUrl or fileUrl parameter key in message tool calls. The normalizeSandboxMediaParams function only checks ["media", "path", "filePath"] keys, while mediaUrl and fileUrl escape normalization entirely. Combined with handlePluginAction dropping mediaLocalRoots from the dispatch context, this enables a full sandbox escape where any agent can read files outside its designated sandbox root.
Details
The vulnerability exists in two files within the messaging pipeline:
1. Incomplete parameter key coverage in normalizeSandboxMediaParams:
In src/infra/outbound/message-action-params.ts, the function iterates over a hardcoded allowlist of parameter keys to validate:
// Line 212
const mediaKeys: Array<"media" | "path" | "filePath"> = ["media", "path", "filePath"];
The mediaUrl and fileUrl parameter keys are not included in this array. These keys are actively used by multiple channel extensions (Discord, Telegram, Slack, Matrix, Twitch) for media attachment handling, but they completely bypass the sandbox path validation performed by resolveSandboxedMediaSource.
2. Dropped mediaLocalRoots in handlePluginAction:
In src/infra/outbound/message-action-runner.ts, the handlePluginAction function dispatches actions to channel plugins but omits mediaLocalRoots from the context:
// Lines 684-697
const handled = await dispatchChannelMessageAction({
channel,
action,
cfg,
params,
accountId: accountId ?? undefined,
requesterSenderId: input.requesterSenderId ?? undefined,
sessionKey: input.sessionKey,
sessionId: input.sessionId,
agentId,
gateway,
toolContext: input.toolContext,
dryRun,
// mediaLocalRoots is MISSING here
});
Despite ChannelMessageActionContext defining mediaLocalRoots?: readonly string[] (in src/channels/plugins/types.core.ts line 478), plugins receive undefined and fall back to getDefaultMediaLocalRoots(), which permits reads of the entire ~/.openclaw/ directory tree — including all agents' workspaces.
Attack chain:
- A sandboxed agent (Agent-A at
~/.openclaw/workspace/agent-a/) calls the message tool with{ mediaUrl: "~/.openclaw/workspace/agent-b/secret.txt" } normalizeSandboxMediaParamsskips themediaUrlkey (not in allowlist)handlePluginActiondispatches withoutmediaLocalRoots- Plugin calls
loadWebMediawith default roots, which allows~/.openclaw/workspace/** - Agent-B's secret file content is read and sent as a channel attachment
PoC
Prerequisites:
- Docker installed
- OpenClaw Docker image built (
openclaw-gateway:latest)
Steps:
- Start the vulnerable gateway container:
cd llm-enhance/cve-finding/Path_Traversal/CVE-2026-27522-Media_Root_Bypass-variant-exp/
docker compose up -d
sleep 5
- Run the exploit:
python3 poc_exploit.py
-
The exploit writes a secret file to
~/.openclaw/workspace/agent-b/secret_key.txtinside the container, then invokesnormalizeSandboxMediaParamswith Agent-A's sandbox policy and{ mediaUrl: <agent-b-secret-path> }. ThemediaUrlkey bypasses normalization, andloadWebMediareads the file successfully. -
Run the control experiment to confirm sandbox works for checked keys:
python3 control-sandbox_enforced.py
Log of Evidence
Exploit output:
=== CVE-2026-27522 Variant: Sandbox Media Root Bypass ===
[*] Container 'openclaw-media-bypass-test' is running
[*] Running exploit script with Bun...
[VULNERABLE] mediaUrl bypassed normalizeSandboxMediaParams!
Agent-A sandboxRoot: /root/.openclaw/workspace/agent-a
mediaUrl targets Agent-B: /root/.openclaw/workspace/agent-b/secret_key.txt
args after normalization: {"mediaUrl":"/root/.openclaw/workspace/agent-b/secret_key.txt"}
[EXPLOITED] Agent-B secret file content: AGENT-B-SECRET-API-KEY-sk-12345abcdef
=== EXPLOIT SUCCESSFUL ===
Agent-A read Agent-B's secret file via mediaUrl, bypassing sandbox.
[+] RESULT: VULNERABLE — mediaUrl bypasses sandbox enforcement
Control experiment output:
=== Control Experiment: Sandbox Enforcement for 'media' Key ===
[*] Container 'openclaw-media-bypass-test' is running
[*] Running control script with Bun...
[SAFE] normalizeSandboxMediaParams blocked 'media' key as expected!
Error: Path escapes sandbox root (/tmp/sandbox-ZKvGQX): /tmp/victim-2cuAOO/secret.txt
=== CONTROL EXPERIMENT PASSED ===
The 'media' parameter IS correctly checked by sandbox enforcement.
Only unchecked keys (mediaUrl, fileUrl) bypass the sandbox.
[+] CONTROL PASSED: 'media' key is correctly enforced by sandbox
Impact
This is a sandbox escape vulnerability. An attacker who can influence an agent's tool calls (via prompt injection, multi-agent interaction, or malicious plugin instruction) can read arbitrary files from other agents' workspaces. This includes:
- API keys and secrets stored in other agents' sandboxes
- Session data and conversation logs
- Configuration files with sensitive credentials
- Any file within the
~/.openclaw/directory tree
This completely defeats the purpose of the multi-agent sandbox isolation feature, which is documented as a security boundary in the project's Docker and sandboxing documentation.
Affected products
- Ecosystem: npm
- Package name: openclaw
- Affected versions: <= 2026.3.14 (current latest)
- Patched versions: <None>
Severity
- Severity: High
- Vector string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weaknesses
- CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Occurrences
| Permalink | Description |
|---|---|
| https://github.com/moltbot/moltbot/blob/main/src/infra/outbound/message-action-params.ts#L206-L227 | The normalizeSandboxMediaParams function with incomplete mediaKeys allowlist — mediaUrl and fileUrl are not checked. |
| https://github.com/moltbot/moltbot/blob/main/src/infra/outbound/message-action-runner.ts#L684-L697 | The handlePluginAction dispatch call that omits mediaLocalRoots from the context passed to dispatchChannelMessageAction. |
| https://github.com/moltbot/moltbot/blob/main/src/channels/plugins/types.core.ts#L478 | The ChannelMessageActionContext type that defines mediaLocalRoots but never receives it from handlePluginAction. |
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.3.24npm install openclaw@2026.3.24 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-35668 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-35668 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-35668. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-35668 in your dependencies?
O3 Security finds CVE-2026-35668 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.