An open API service providing security vulnerability metadata for many open source software ecosystems.

GSA_kwCzR0hTQS1mZzNtLXZocnItOGdqNs4ABTFk

Moderate CVSS: 5.1

OpenClaw has Windows Lobster shell fallback command injection in constrained fallback path

Affected Packages Affected Versions Fixed Versions
npm:openclaw
PURL: pkg:npm/openclaw
>= 2026.1.21, <= 2026.2.17 2026.2.19
0 Dependent packages
0 Dependent repositories
6,021,905 Downloads last month

Affected Version Ranges

All affected versions

2026.1.29, 2026.1.29-beta.1, 2026.1.29-beta.2, 2026.1.29-beta.3, 2026.1.29-beta.4, 2026.1.29-beta.5, 2026.1.29-beta.7, 2026.1.30, 2026.2.1, 2026.2.2, 2026.2.2-1, 2026.2.2-2, 2026.2.2-3, 2026.2.3, 2026.2.3-1, 2026.2.6, 2026.2.6-1, 2026.2.6-2, 2026.2.6-3, 2026.2.9, 2026.2.12, 2026.2.13, 2026.2.14, 2026.2.15, 2026.2.17

All unaffected versions

0.0.1, 2026.2.19, 2026.2.21, 2026.2.22, 2026.2.23, 2026.2.24, 2026.2.25, 2026.2.26, 2026.3.1, 2026.3.2, 2026.3.7, 2026.3.8, 2026.3.11

Summary

On Windows, the Lobster extension previously retried certain spawn failures (ENOENT/EINVAL) with shell: true for wrapper compatibility. In that fallback path, tool-provided arguments could be interpreted by cmd.exe if fallback was triggered.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Latest published version at triage: 2026.2.17
  • Affected range: >= 2026.1.21 <= 2026.2.17
  • Patched version: 2026.2.19 (pre-set for next release)

Fix

The Windows shell fallback was removed. Wrapper compatibility is preserved by resolving .cmd/.bat shims to a concrete Node entrypoint (or executable) and executing with explicit argv (no shell). If a safe entrypoint cannot be resolved, execution now fails closed with a guided error.

Fix Commit(s)

  • ba7be018da354ea9f803ed356d20464df0437916

Severity Context

This issue requires Windows plus fallback-triggering conditions, and argument control through a local operator-defined workflow.

OpenClaw thanks @tdjackey for reporting.

References: