OpenClaw anfällig für sensible Offenlegung von Dateien über stageSandboxMedia

The vulnerability stems from a flaw in stageSandboxMedia which accepts arbitrary absolute paths when iMessage remote attachment fetching is enabled. This allows an attacker to bypass intended security controls and use SCP to copy files outside of the expected iMessage attachment directories onto the remote host. Successful exploitation could lead to unauthorized access to sensitive data stored on the system, potentially including configuration files, source code, or other confidential information. The impact is primarily focused on confidentiality, as the attacker can read files, but not directly execute code.

Applications utilizing openclaw for iMessage integration, particularly those with channels.imessage.remoteHost enabled, are at risk. Shared hosting environments where multiple applications share the same server and file system are also potentially vulnerable, as a compromise in one application could lead to the exposure of data from others.

• nodejs / supply-chain:

  npm list openclaw

• nodejs / supply-chain:

  npm audit openclaw

• generic web: Inspect Node.js application configuration files for the presence of channels.imessage.remoteHost set to true.

1. 2026-03-03Disclosure

   disclosure

2. 2026-03-03Patch

   patch

1. Reserviert2026-03-10
2. Veröffentlicht2026-03-03
3. Geändert2026-03-27
4. EPSS aktualisiert2026-03-27

The primary mitigation is to upgrade to version 2026.2.19 or later, which includes remote attachment path validation. If upgrading is not immediately feasible, disable iMessage remote attachment fetching by setting channels.imessage.remoteHost to false. Monitor system logs for unusual SCP activity or file access attempts. Consider implementing a Web Application Firewall (WAF) to filter requests containing potentially malicious file paths. There are no specific Sigma or YARA rules available at this time, but monitoring for SCP connections to unexpected locations is recommended.