CVE-2026-32030

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

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.

Confidentiality impact. An attacker who can influence inbound attachment path metadata may disclose files readable by the OpenClaw process on the configured remote host.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-32030 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.19); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-32030? CVE-2026-32030 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions < 2026.2.19. It is fixed in 2026.2.19. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-32030? CVE-2026-32030 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32030? openclaw (npm) versions < 2026.2.19 is affected.
4. Is there a fix for CVE-2026-32030? Yes. CVE-2026-32030 is fixed in 2026.2.19. Upgrade to this version or later.
5. Is CVE-2026-32030 exploitable, and should I be worried? Whether CVE-2026-32030 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32030 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32030? Upgrade openclaw to 2026.2.19 or later.