Skip to content

Instantly share code, notes, and snippets.

@alon710
Created March 11, 2026 20:10
Show Gist options
  • Select an option

  • Save alon710/42f2baf7f8222d8e21a959d90dfc0bba to your computer and use it in GitHub Desktop.

Select an option

Save alon710/42f2baf7f8222d8e21a959d90dfc0bba to your computer and use it in GitHub Desktop.
CVE-2026-32094: CVE-2026-32094: Argument Injection via Incomplete Shell Escaping in shescape - CVE Security Report

CVE-2026-32094: CVE-2026-32094: Argument Injection via Incomplete Shell Escaping in shescape

CVSS Score: 6.9 Published: 2026-03-11 Full Report: https://cvereports.com/reports/CVE-2026-32094

Summary

The shescape library prior to version 2.1.10 fails to properly escape square brackets when targeting Unix-like shells. This omission allows attackers to leverage shell pathname expansion (globbing) to perform argument injection attacks, potentially exposing sensitive local files.

TL;DR

shescape < 2.1.10 is vulnerable to argument injection due to unescaped square brackets, allowing attackers to exploit shell globbing for unauthorized file access.

Exploit Status: POC

Technical Details

  • CWE: CWE-200
  • Attack Vector: Network
  • CVSS v4.0: 6.9
  • Exploit Status: Proof of Concept
  • CISA KEV: False
  • Impact: Information Exposure

Affected Systems

  • shescape < 2.1.10
  • shescape: < 2.1.10 (Fixed in: 2.1.10)

Mitigation

  • Upgrade shescape to version 2.1.10
  • Enclose all interpolated shell variables in single quotes
  • Implement strict input validation to reject shell metacharacters

Remediation Steps:

  1. Identify all projects utilizing shescape via npm ls shescape or yarn why shescape.
  2. Update package.json to require shescape version ^2.1.10.
  3. Run npm install or yarn install to update the dependency tree.
  4. Review all instances of shescape.escape() usage to ensure the resulting variables are properly quoted in the final command string.

References


Generated by CVEReports - Automated Vulnerability Intelligence

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment