VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

shescape: vulnerability history, versions and safety

shescape is a package in the npm ecosystem. Vulert records 14 vulnerabilities for it across 63 releases, from Mar 2021 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded C2 H5 M4 L3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
6 in the last 12 months

Most recent disclosure 24 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all shescape vulnerabilities

Vulert verdict on shescape 3.0.2 i

Updated on 23 Oct 2026

Good news: 3.0.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 14.

Package health score 59/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

What to do: Stay on 3.0.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.0.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.0.2 — unaffected i
  • Vulnerabilities on record 14 over 5 years · 6 in the last year i
  • Latest disclosure 24 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 9 i
  • OpenSSF scorecard 7/10 i
  • Last release 2 months ago i
  • Licence MPL-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for shescape, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.0.2 01 Aug 2026 none MPL-2.0 — Details →
2.1.15 01 Aug 2026 none MPL-2.0 — Details →
3.0.1 22 Jul 2026 none MPL-2.0 — Details →
2.1.14 22 Jul 2026 none MPL-2.0 — Details →
3.0.0 13 Jun 2026 none MPL-2.0 — Details →
2.1.13 13 Jun 2026 C1 H1 M2 MPL-2.0 Yes Details →
2.1.12 06 May 2026 C1 H1 M2 MPL-2.0 Yes Details →
2.1.11 07 Apr 2026 C1 H1 M2 MPL-2.0 Yes Details →
2.1.10 10 Mar 2026 C1 M2 MPL-2.0 Yes Details →
2.1.9 06 Mar 2026 C1 M3 MPL-2.0 Yes Details →
2.1.8 25 Jan 2026 C1 M3 L1 MPL-2.0 Yes Details →
2.1.7 22 Nov 2025 C1 M3 L1 MPL-2.0 Yes Details →
2.1.6 14 Jul 2025 C1 M3 L1 MPL-2.0 Yes Details →
2.1.5 19 Jun 2025 C1 M3 L1 MPL-2.0 Yes Details →
2.1.4 01 Jun 2025 C1 M3 L1 MPL-2.0 Yes Details →
2.1.3 11 May 2025 C1 M3 L1 MPL-2.0 Yes Details →
2.1.2 25 Mar 2025 C1 M3 L1 MPL-2.0 Yes Details →
2.1.1 01 May 2024 C1 M3 L2 MPL-2.0 Yes Details →
2.1.0 23 Dec 2023 C1 M3 L2 MPL-2.0 Yes Details →
2.0.2 19 Nov 2023 C1 M3 L2 MPL-2.0 Yes Details →
2.0.1 28 Oct 2023 C1 M3 L2 MPL-2.0 Yes Details →
2.0.0 07 Sep 2023 C1 M3 L2 MPL-2.0 Yes Details →
2.0.0-rc3 22 Aug 2023 C1 M3 L2 MPL-2.0 Yes Details →
1.7.4 21 Aug 2023 C1 M3 L2 MPL-2.0 Yes Details →
2.0.0-rc2 09 Aug 2023 C1 M3 L2 MPL-2.0 Yes Details →
1.7.3 07 Aug 2023 C1 H1 M3 L2 MPL-2.0 Yes Details →
2.0.0-rc1 10 Jul 2023 C1 M3 L2 MPL-2.0 Yes Details →
1.7.2 07 Jul 2023 C1 H1 M3 L2 MPL-2.0 Yes Details →
1.7.1 21 Jun 2023 C1 H1 M3 L1 MPL-2.0 Yes Details →
1.7.0 12 Jun 2023 C1 H1 M3 L2 MPL-2.0 Yes Details →
1.6.7 29 May 2023 C1 H1 M3 L2 MPL-2.0 Yes Details →
1.6.6 20 Apr 2023 C1 H1 M3 L2 MPL-2.0 Yes Details →
1.6.5 26 Jan 2023 C1 H1 M3 L2 MPL-2.0 Yes Details →
1.6.4 22 Jan 2023 C1 H1 M3 L2 MPL-2.0 Yes Details →
1.6.3 21 Jan 2023 C1 H1 M3 L2 MPL-2.0 Yes Details →
1.6.2 03 Jan 2023 C1 H1 M3 L2 MPL-2.0 Yes Details →
1.6.1 25 Oct 2022 C1 H1 M3 L2 MPL-2.0 Yes Details →
1.6.0 15 Oct 2022 C1 H2 M3 L2 MPL-2.0 Yes Details →
1.5.10 21 Aug 2022 C1 H2 M3 L2 MPL-2.0 Yes Details →
1.5.9 28 Jul 2022 C1 H1 M3 L2 MPL-2.0 Yes Details →
1.5.8 15 Jul 2022 C1 H1 M3 L2 MPL-2.0 Yes Details →
1.5.7 06 Jul 2022 C2 H2 M3 L2 MPL-2.0 Yes Details →
1.5.6 02 Jul 2022 C2 H2 M3 L2 MPL-2.0 Yes Details →
1.5.5 05 Jun 2022 C2 H2 M3 L2 MPL-2.0 Yes Details →
1.5.4 07 Mar 2022 C2 H2 M3 L2 MPL-2.0 Yes Details →
1.5.3 06 Mar 2022 C2 H2 M3 L2 MPL-2.0 Yes Details →
1.5.2 23 Feb 2022 C2 H2 M3 L2 MPL-2.0 Yes Details →
1.5.1 20 Feb 2022 C2 H2 M3 L2 MPL-2.0 Yes Details →
1.5.0 15 Feb 2022 C2 H2 M4 L2 MPL-2.0 Yes Details →
1.4.0 08 Feb 2022 C2 H2 M4 L2 MPL-2.0 Yes Details →
1.3.3 15 Jan 2022 C1 H2 M3 L2 MPL-2.0 Yes Details →
1.3.2 05 Jan 2022 C1 H2 M3 L2 MPL-2.0 Yes Details →
1.3.1 06 Dec 2021 C1 H2 M3 L2 MPL-2.0 Yes Details →
1.3.0 05 Dec 2021 C1 H2 M3 L2 MPL-2.0 Yes Details →
1.2.1 24 Apr 2021 C1 H2 M3 L2 MPL-2.0 Yes Details →
1.2.0 16 Apr 2021 C1 H2 M3 L2 MPL-2.0 Yes Details →
1.1.3 13 Mar 2021 C1 H2 M3 L2 MPL-2.0 Yes Details →
1.1.2 07 Jan 2021 C1 H3 M3 L2 MPL-2.0 Yes Details →
1.1.1 30 Dec 2020 C1 H3 M3 L2 MPL-2.0 Yes Details →
1.1.0 22 Dec 2020 C1 H3 M3 L2 MPL-2.0 Yes Details →
1.0.0 10 Dec 2020 C1 H3 M3 L2 MPL-2.0 Yes Details →
0.4.1 09 Dec 2020 C1 H3 M3 L2 MPL-2.0 Yes Details →
0.4.0 08 Dec 2020 C1 H3 M3 L2 MPL-2.0 Yes Details →
0.3.1 07 Dec 2020 C1 H3 M3 L2 MPL-2.0 Yes Details →
0.3.0 07 Dec 2020 C1 H3 M3 L2 MPL-2.0 Yes Details →
0.2.1 07 Nov 2020 C1 H3 M3 L2 MPL-2.0 Yes Details →
0.2.0 07 Nov 2020 C1 H3 M3 L2 MPL-2.0 Yes Details →
0.1.0 06 Nov 2020 C1 H3 M3 L2 MPL-2.0 Yes Details →

All 68 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 4
  • 2023 2
  • 2025 1
  • 2026 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 6 of the 14 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for shescape

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-31180: shescape vulnerable to insufficient escaping of whitespace 9.8 critical 1.5.8 15 Jul 2022
Critical Shell Injection Vulnerability in Shescape Package on Windows CMD 9.2 critical 2.1.14 24 Jul 2026
Quadratic-time Denial of Service in Shescape Package 8.7 high 2.1.14 24 Jul 2026
CVE-2023-40185: Shescape on Windows escaping may be bypassed in threaded context 8.6 high 1.7.4 22 Aug 2023
CVE-2022-31179: Vulnerability in shescape package allows command injection 8.1 high 1.5.8 15 Jul 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About shescape

Is shescape safe to use?

Vulert records 14 vulnerabilities for shescape in npm: 2 critical, 5 high, 4 medium and 3 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is shescape's Vulert package health score?

Vulert scores shescape 59/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of shescape affected?

No. 3.0.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of shescape should I use?

3.0.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does shescape have?

14 vulnerabilities are recorded for shescape in the npm ecosystem: 2 critical, 5 high, 4 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new shescape vulnerabilities disclosed?

6 vulnerabilities were recorded for shescape in the last 12 months, and the oldest entry in this database dates to 18 Mar 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of shescape are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor shescape for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the shescape version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.