Every CVESearch/Get API key

GHSA-2mc2-g238-722j

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

5.3 MediumFix available

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.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
None
Integrity
Low
Availability
None

What each source reports

GitHub Advisories Score used5.3

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

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.

Record
GHSA-2mc2-g238-722j
CVSS 4.0
5.3 MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Weakness
CWE-78, CWE-295
Updated
2026-11-02
OSV5.3

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

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.

Record
GHSA-2mc2-g238-722j
CVSS 4.0
5.3 MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Weakness
CWE-295, CWE-78
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
openclaw
npm
through 2026.2.17
2026.2.19
openclaw
npm
before 2026.2.19
2026.2.19

History

History
RecordedChangedSources
first indexedGitHub Advisories, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

GHSA-2mc2-g238-722j is a medium vulnerability (CVSS 5.3) in openclaw, published March 3, 2026. No source lists public exploit code. Fixed in openclaw 2026.2.19.

References

PagesAll vulnerabilitiesBrowseDocsSourcesGuideGet API key
MoveEnter Open