How severe is GHSA-2mc2-g238-722j?

No CVSS score has been assigned to GHSA-2mc2-g238-722j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2mc2-g238-722j?

GHSA-2mc2-g238-722j affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-2mc2-g238-722j?

Update openclaw to 2026.2.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2mc2-g238-722j is resolved across your whole dependency graph.

How do I detect GHSA-2mc2-g238-722j in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2mc2-g238-722j 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-2mc2-g238-722j?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2mc2-g238-722j can be triaged on real exposure rather than presence alone.

Is GHSA-2mc2-g238-722j actively exploited in the wild?

No public exploit code has been indexed for GHSA-2mc2-g238-722j 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.

When was GHSA-2mc2-g238-722j published, and has it been updated?

GHSA-2mc2-g238-722j was published on March 3, 2026 and was last updated on March 4, 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

Not in CISA KEV

GHSA-2mc2-g238-722j — openclaw

Fix: openclaw/openclaw@49d0def

GHSA-2mc2-g238-722j is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw affected by iMessage remote attachment SCP hardening (strict host-key checks and remoteHost validation)

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.5Mdownloads / week

Description

Summary

Remote iMessage attachment fetches used SCP with trust-on-first-use host-key behavior and accepted unvalidated remote host tokens.

Before the fix:

SCP used StrictHostKeyChecking=accept-new in the remote attachment path.
channels.imessage.remoteHost was not validated as a strict SSH host token.

Impact

In remote iMessage deployments that use SCP attachment fetching, a first-connection MITM/DNS-poisoning scenario could cause the wrong host key to be trusted. Unsafe remote host token values could also alter SCP argument semantics.

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version currently affected: 2026.2.17
Vulnerable range (structured field): <= 2026.2.17
Patched version (pre-set for next release): >= 2026.2.19

Fix

The fix hardens remote attachment SSH/SCP handling by:

requiring StrictHostKeyChecking=yes for SCP and SSH tunnel paths,
adding strict remoteHost normalization/validation,
adding -- argument barrier for SCP remote source parsing,
validating channels.imessage.remoteHost in config schema,
rejecting unsafe auto-detected host tokens at runtime.

Fix Commit(s)

Pushed to main: 49d0def6d1e88f002026b1d2a35aa615d48a751a

OpenClaw thanks @allsmog for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.19`npm install openclaw@2026.2.19`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2mc2-g238-722j 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2mc2-g238-722j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2mc2-g238-722j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Remote iMessage attachment fetches used SCP with trust-on-first-use host-key behavior and accepted unvalidated remote host tokens. Before the fix: - SCP used `StrictHostKeyChecking=accept-new` in the remote attachment path. - `channels.imessage.remoteHost` was not validated as a strict SSH host token. ## Impact In remote iMessage deployments that use SCP attachment fetching, a first-connection MITM/DNS-poisoning scenario could cause the wrong host key to be trusted. Unsafe remote host token values could also alter SCP argument semantics. ## Affected Packages / Versions - Packa

O3 Security · Impact-Aware SCA

Is GHSA-2mc2-g238-722j in your dependencies?

O3 Security finds GHSA-2mc2-g238-722j across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works