How severe is GHSA-g2f6-pwvx-r275?

No CVSS score has been assigned to GHSA-g2f6-pwvx-r275 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g2f6-pwvx-r275?

GHSA-g2f6-pwvx-r275 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-g2f6-pwvx-r275?

Update openclaw to 2026.3.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g2f6-pwvx-r275 is resolved across your whole dependency graph.

How do I detect GHSA-g2f6-pwvx-r275 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-g2f6-pwvx-r275 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-g2f6-pwvx-r275?

O3 pinpoints whether GHSA-g2f6-pwvx-r275 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-g2f6-pwvx-r275 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g2f6-pwvx-r275 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-g2f6-pwvx-r275?

GHSA-g2f6-pwvx-r275 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-g2f6-pwvx-r275 published, and has it been updated?

GHSA-g2f6-pwvx-r275 was published on March 16, 2026 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-g2f6-pwvx-r275

GHSA-g2f6-pwvx-r275 is a OS Command Injection vulnerability in openclaw. O3 Security confirms whether GHSA-g2f6-pwvx-r275 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpneClaw accepts unsanitized iMessage attachment paths which allowed SCP remote-path command injection

Also known asCVE-2026-32917

Published

Mar 16, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

3.1Mdownloads / week

Description

Summary

openclaw versions <= 2026.3.12 accepted unsanitized iMessage remote attachment paths when staging files over SCP, allowing shell metacharacters in the remote path operand.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.3.12
Fixed version: 2026.3.13

Details

The vulnerable path was the remote attachment staging flow in src/auto-reply/reply/stage-sandbox-media.ts. When ctx.MediaRemoteHost was set, OpenClaw staged the attachment by spawning /usr/bin/scp against <remoteHost>:<remotePath>. In affected releases, the remote host was normalized but the remote attachment path was not validated for shell metacharacters before being passed to the SCP remote operand. A sender-controlled iMessage attachment filename containing shell metacharacters could therefore trigger command execution on the configured remote host when remote attachment staging was enabled.

This issue is in scope under OpenClaw's trust model because it crosses an inbound content boundary into host command execution on a configured remote attachment host.

Fix

[email protected] validates the SCP remote path before spawning scp. Current code calls normalizeScpRemotePath(...) and rejects paths containing shell metacharacters instead of passing them through to the remote shell.

Regression coverage exists in src/auto-reply/reply.stage-sandbox-media.scp-remote-path.test.ts (rejects remote attachment filenames with shell metacharacters before spawning scp).

Fix Commit(s)

a54bf71b4c0cbe554a84340b773df37ee8e959de

Thanks @lintsinghua for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.3.13

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.3.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g2f6-pwvx-r275 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-g2f6-pwvx-r275 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-g2f6-pwvx-r275. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary `openclaw` versions `<= 2026.3.12` accepted unsanitized iMessage remote attachment paths when staging files over SCP, allowing shell metacharacters in the remote path operand. ### Affected Packages / Versions - Package: `openclaw` (`npm`) - Affected versions: `<= 2026.3.12` - Fixed version: `2026.3.13` ### Details The vulnerable path was the remote attachment staging flow in `src/auto-reply/reply/stage-sandbox-media.ts`. When `ctx.MediaRemoteHost` was set, OpenClaw staged the attachment by spawning `/usr/bin/scp` against `<remoteHost>:<remotePath>`. In affected releases, the remo

O3 Security · Impact-Aware SCA

Is GHSA-g2f6-pwvx-r275 in your dependencies?

O3 detects GHSA-g2f6-pwvx-r275 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works