Quick answers
- Is CVE-2026-30916 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30916 being exploited in the wild.
- How severe is CVE-2026-30916?
- Medium severity, with a CVSS score of 4, published 7 March 2026.
- Which products and versions are affected?
- shescape (npm) SEMVER:introduced=0,fixed=2.1.9.
- Is there a fix for CVE-2026-30916?
- Yes. shescape (npm): upgrade to 2.1.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-30916 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-30916?
- Check whether you run shescape (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- shescape (npm): upgrade to 2.1.9 or later
npm install shescape@2.1.9
Technical details
This vulnerability stems from inadequate symlink resolution in Shescape's shell identification logic. When a shell executable path is configured as a symlink to another symlink (a chain), the library fails to correctly identify the actual shell type, leading to incorrect escaping rules being applied. An attacker who can influence the shell configuration (via symlink chains they control) can cause the library to apply escaping rules for the wrong shell, enabling command injection. The vulnerability requires specific system configuration (shell path pointing to a symlink chain) and affects versions prior to 2.1.9. A patch is available in v2.1.9 which properly resolves symlink chains.
Affected products
- ericcornelissen shescape prior to 2.1.9
Identifiers
- CVE-2026-30916
- GHSA-6f6w-6j58-rq76
Timeline
- 2026-03-07: disclosed
- 2026-03-20: patched: v2.1.9 released with fix