Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-x9cf-3w63-rpq9
No affected components available
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.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard