NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · OpenClaw

CVE-2026-32030: OpenClaw vulnerable to sensitive file disclosure via stageSandboxMedia

highCVSS 4.0 8.7 · 3.1 7.5GHSA-x9cf-3w63-rpq9

With iMessage remote attachments enabled, OpenClaw's `stageSandboxMedia` accepted any absolute path and copied it over SCP into local staging. Someone who can tamper with attachment path metadata can pull any file the OpenClaw process can read on the remote host. Upgrade to openclaw 2026.2.19.

Published Mar 3, 2026 · Updated Mar 27, 2026 · Analysis Oct 31, 2026

What an attacker can do

When channels.imessage.remoteHost is set, OpenClaw fetches iMessage attachments from a remote Mac with SCP. stageSandboxMedia did not check that the path pointed into the iMessage attachment directory. If a non-attachment path reached this flow, the file at that path was copied into local staging, where the agent or the attacker's next step can read it.

The attacker needs to inject or tamper with attachment path metadata in an inbound message. They need no account on the host. The CVSS vectors show network access, no privileges and high confidentiality impact only. What leaks is whatever the OpenClaw process can read on the remote host: SSH keys, tokens, documents and config files.

It applies only when three conditions hold: channels.imessage.includeAttachments=true, remote attachment mode is active (configured or auto-detected), and the attacker can influence the path metadata. The maintainers rate it medium on those preconditions.

Who is affected

openclaw (npm) versions up to and including 2026.2.17, with the package data listing everything below 2026.2.19 as vulnerable. You are exposed if channels.imessage.includeAttachments is true and channels.imessage.remoteHost is configured or auto-detected.

npm ls openclaw

Then check the iMessage channel section of your OpenClaw config for those two settings.

openclaw

Ecosystem
npm
Affected
< 2026.2.19
Fixed in
2026.2.19
Check
npm ls openclaw

How to fix it

Upgrade to openclaw 2026.2.19:

npm install [email protected]

The fix adds attachmentRoots for local files and remoteAttachmentRoots for SCP mode. The default is /Users/*/Library/Messages/Attachments. The monitor drops attachments outside the roots, and stageSandboxMedia refuses remote paths outside remoteAttachmentRoots. Roots must be absolute paths.

The advisory also lists two mitigations. Disable iMessage attachment ingestion if you do not need remote attachments. Run OpenClaw with least privilege on the remote host.

How to tell if you were hit

After the upgrade, blocked attempts log "dropping inbound attachment outside allowed roots" and "Blocking remote media staging from disallowed attachment path" at verbose level. On older versions, look in the staging directory for files that are not iMessage attachments, and check the remote host's SSH logs for scp reads of sensitive paths such as ~/.ssh or config files. Beam records agent file access, which can show reads of staged files.

Original advisory

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

  1. iMessage attachments enabled (channels.imessage.includeAttachments=true), and
  2. remote attachment mode active (channels.imessage.remoteHost configured or auto-detected), and
  3. 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.

Questions

Does CVE-2026-32030 affect OpenClaw without iMessage?

No. It needs the iMessage channel with includeAttachments on and remote attachment mode active, set by channels.imessage.remoteHost or auto-detected.

What files can an attacker read?

Any file the OpenClaw process can read on the configured remote host. The impact is confidentiality only, per the advisory.

Can I mitigate without upgrading?

Yes, partly. The advisory says to disable iMessage attachment ingestion if remote attachments are not required, and to run OpenClaw under least privilege on the remote host.

References

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. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries