VulnerabilityPublished 11 Mar 2026Updated 12 Mar 2026

CVE-2026-32094: ericcornelissen shescape · Information Exposure

Affects ericcornelissen shescapeSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 2.1.10 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.1.10

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade ericcornelissen shescape to 2.1.10.

Affected software

Product	Affected	Fixed in
ericcornelissenshescape	Affected <2.1.10	Fixed in 2.1.10

AI-suggested

To mitigate this vulnerability, organizations should immediately upgrade shescape to version 2.1.10 or later, where the escape() function properly escapes square-bracket glob syntax. Additionally, developers should avoid directly interpolating untrusted input into shell commands, even when using escaping libraries. Employ safer alternatives such as passing arguments as arrays to spawn or exec functions that do not invoke shell parsing. Implement strict input validation and sanitization to reject or neutralize glob patterns and other shell metacharacters. Conduct code audits to identify all usages of shescape and shell command construction in the codebase. Where possible, replace shell command invocations with native APIs or libraries that do not rely on shell parsing. Monitor logs for suspicious input patterns that may indicate exploitation attempts. Finally, maintain an updated inventory of dependencies and apply security patches promptly to reduce exposure to known vulnerabilities.

Description

CVE-2026-32094 is a medium severity vulnerability in the JavaScript library shescape prior to version 2.1.10. The flaw arises because the escape() function does not properly escape square-bracket glob syntax used by shells like Bash, BusyBox sh, and Dash. This allows attacker-controlled input containing patterns like secret[12] to expand into multiple filesystem matches instead of a single literal argument. Consequently, sensitive information may be exposed if these expanded matches reveal confidential file paths. The vulnerability requires no authentication or user interaction and can be exploited remotely by injecting crafted input into shell commands that use shescape. The issue is fixed in shescape version 2.1.10.

Impact

The primary impact of this vulnerability is the unintended exposure of sensitive filesystem information due to shell glob expansion of attacker-controlled input. Organizations that use shescape in JavaScript applications to build shell commands with untrusted input risk leaking confidential file paths or data. This can aid attackers in reconnaissance or further exploitation by revealing the presence and names of sensitive files. Since the vulnerability does not allow direct code execution or privilege escalation, the impact is limited to confidentiality breaches and potential information disclosure. However, in environments where shell commands control critical systems or handle sensitive data, this exposure can facilitate more severe attacks. The vulnerability is exploitable remotely without authentication, increasing its risk profile. Organizations relying on vulnerable versions of shescape in web applications, CI/CD pipelines, or automation scripts that invoke shell commands are particularly at risk. The absence of known exploits in the wild suggests limited current exploitation but also highlights the importance of timely patching to prevent future attacks.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Mar 2026, 02:18 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats