GHSA-2mc2-g238-722j: Openclaw OpenClaw Affected By IMessage Remote Vulnerability

MODERATE
CWE-78 CWE-295
Published
Advisory Summary

GHSA-2mc2-g238-722j is a MODERATE openclaw affected by imessage remote vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Openclaw libraries in the npm ecosystem. The issue involves openclaw affected by imessage remote attachment scp hardening (strict host-key checks and remotehost validation). Remediation is available by upgrading affected packages to version 2026.2.19.

GHSA-2mc2-g238-722j at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-2mc2-g238-722j
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product Openclaw
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-2mc2-g238-722j

To remediate this vulnerability, upgrade all affected Openclaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openclaw fixed: 2026.2.19
npm install openclaw@2026.2.19
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls openclaw

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-2mc2-g238-722j, inspect your project dependencies using npm:

npm ls openclaw

Analyze the terminal output to locate any version of Openclaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.2.19), your application is affected.

Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Openclaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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.

GHSA-2mc2-g238-722j Affected Openclaw Versions

1 component(s)
Fixed Versions:
2026.2.19
Product / Package Ecosystem Affected Versions Fixed Version
openclaw
npm
< 2026.2.19
2026.2.19

References

Frequently Asked Questions

What is GHSA-2mc2-g238-722j?
GHSA-2mc2-g238-722j is a security vulnerability in Openclaw involving OpenClaw affected by iMessage remote attachment SCP hardening (strict host-key checks and remoteHost validation) under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which Openclaw versions are affected?
Affected versions include releases prior to 2026.2.19 across affected packages: openclaw.
What version fixes GHSA-2mc2-g238-722j?
Upgrading to 2026.2.19 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openclaw affected?
Yes, openclaw is affected in releases prior to 2026.2.19. Upgrade your dependency to 2026.2.19 or later.
What CWE is associated with GHSA-2mc2-g238-722j?
GHSA-2mc2-g238-722j is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.).
How can I check npm dependencies for GHSA-2mc2-g238-722j?
Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2mc2-g238-722j",
  "modified" : "2026-03-03T21:35:21Z",
  "published" : "2026-03-03T21:35:21Z",
  "aliases" : [ ],
  "summary" : "OpenClaw affected by iMessage remote attachment SCP hardening (strict host-key checks and remoteHost validation)",
  "details" : "## Summary\n\nRemote iMessage attachment fetches used SCP with trust-on-first-use host-key behavior and accepted unvalidated remote host tokens.\n\nBefore the fix:\n- SCP used `StrictHostKeyChecking=accept-new` in the remote attachment path.\n- `channels.imessage.remoteHost` was not validated as a strict SSH host token.\n\n## Impact\n\nIn 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.\n\n## Affected Packages / Versions\n\n- Package: `openclaw` (npm)\n- Latest published npm version currently affected: `2026.2.17`\n- Vulnerable range (structured field): `<= 2026.2.17`\n- Patched version (pre-set for next release): `>= 2026.2.19`\n\n## Fix\n\nThe fix hardens remote attachment SSH/SCP handling by:\n- requiring `StrictHostKeyChecking=yes` for SCP and SSH tunnel paths,\n- adding strict `remoteHost` normalization/validation,\n- adding `--` argument barrier for SCP remote source parsing,\n- validating `channels.imessage.remoteHost` in config schema,\n- rejecting unsafe auto-detected host tokens at runtime.\n\n## Fix Commit(s)\n\n- Pushed to `main`: 49d0def6d1e88f002026b1d2a35aa615d48a751a\n\nOpenClaw thanks @allsmog for reporting.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.2.19"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2026.2.17"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-2mc2-g238-722j"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/49d0def6d1e88f002026b1d2a35aa615d48a751a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-295", "CWE-78" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-03T21:35:21Z",
    "nvd_published_at" : null
  }
}