CVE-2026-32030: OpenClaw vulnerable to sensitive file disclosure via stageSandboxMedia
Summary When iMessage remote attachment fetching is enabled (channels.imessage.remoteHost), stageSandboxMedia accepted arbitrary absolute paths and used SCP to copy them into local staging. If a non-attachment path reaches this flow, files outside expected iMessage attachment directories on the remote host can be staged.
Published Mar 3, 2026 · Updated Mar 27, 2026
Affected packages
openclaw
- Ecosystem
- npm
- Affected
- < 2026.2.19
- Fixed in
- 2026.2.19
- Check
npm ls openclaw
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When iMessage remote attachment fetching is enabled (channels.imessage.remoteHost), stageSandboxMedia accepted arbitrary absolute paths and used SCP to copy them into local staging.
If a non-attachment path reaches this flow, files outside expected iMessage attachment directories on the remote host can be staged.
Affected Packages / Versions
- Package:
openclaw - Affected: up to and including
2026.2.17(latest npm version as of February 19, 2026) - Fixed: pending next release with remote attachment path validation
Impact
Confidentiality impact. An attacker who can influence inbound attachment path metadata may disclose files readable by the OpenClaw process on the configured remote host.
Attack Preconditions
- iMessage attachments enabled (
channels.imessage.includeAttachments=true), and - remote attachment mode active (
channels.imessage.remoteHostconfigured or auto-detected), and - attacker can inject/tamper with attachment path metadata.
Given these preconditions, this advisory is assessed as medium severity.
Fix Commit(s)
1316e5740382926e45a42097b4bfe0aef7d63e8e
Release Process Note
patched_versions should be set to the next released npm version that includes remote attachment path validation, then the advisory can be published.
Mitigation
- Upgrade to the first release that includes remote attachment path validation.
- If remote attachments are not required, disable iMessage attachment ingestion.
- Run OpenClaw under least privilege on the remote host.
OpenClaw thanks @zpbrent for reporting.
Credited to zpbrent.
References
- https://github.com/openclaw/openclaw/security/advisories/GHSA-x9cf-3w63-rpq9
- https://github.com/openclaw/openclaw/commit/1316e5740382926e45a42097b4bfe0aef7d63e8e
- https://nvd.nist.gov/vuln/detail/CVE-2026-32030
- https://www.vulncheck.com/advisories/openclaw-sensitive-file-disclosure-via-stagesandboxmedia-path-traversal
- https://github.com/advisories/GHSA-x9cf-3w63-rpq9
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026CVE-2026-53812
OpenClaw's browser act interactions could bypass private-network navigation checks
medium7.7Jul 2, 2026
