VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

shell-quote: vulnerability history, versions and safety

shell-quote is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 32 releases, from Feb 2019 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C4 H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 06 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all shell-quote vulnerabilities

Vulert verdict on shell-quote 1.12.0 i

Updated on 22 Oct 2026

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

Package health score 69/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 1.12.0 — unaffected i
  • Vulnerabilities on record 5 over 7 years · 3 in the last year i
  • Latest disclosure 06 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 74,836 packages i
  • Stars 66 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 shell-quote, 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
1.12.0 02 Oct 2026 none MIT — Details →
1.11.0 29 Sep 2026 none MIT — Details →
1.10.0 10 Jul 2026 C1 MIT Yes Details →
1.9.0 25 Jun 2026 C1 MIT Yes Details →
1.8.4 22 May 2026 C1 H1 MIT Yes Details →
1.8.3 02 Jun 2025 C1 H1 MIT Yes Details →
1.8.2 27 Nov 2024 C1 H1 MIT Yes Details →
1.8.1 07 Apr 2023 C1 H1 MIT Yes Details →
1.8.0 31 Jan 2023 C1 H1 MIT Yes Details →
1.7.4 13 Oct 2022 C1 H1 MIT Yes Details →
1.7.3 21 Oct 2021 C1 H1 MIT Yes Details →
1.7.2 01 Sep 2019 C2 H1 MIT Yes Details →
1.7.1 13 Aug 2019 C2 H1 MIT Yes Details →
1.7.0 13 Aug 2019 C2 H1 MIT Yes Details →
1.6.3 13 Aug 2019 C2 H1 MIT Yes Details →
1.6.2 13 Aug 2019 C2 H1 MIT Yes Details →
1.6.1 17 Jun 2016 C2 H1 MIT Yes Details →
1.6.0 24 Apr 2016 C3 H1 MIT Yes Details →
1.5.0 16 Mar 2016 C3 H1 MIT Yes Details →
1.4.3 08 Mar 2015 C3 H1 MIT Yes Details →
1.4.2 20 Jul 2014 C3 H1 MIT Yes Details →
1.4.1 25 Dec 2013 C3 H1 MIT Yes Details →
1.4.0 18 Oct 2013 C3 H1 MIT Yes Details →
1.3.3 24 Jun 2013 C3 H1 MIT Yes Details →
1.3.2 24 Jun 2013 C3 H1 MIT Yes Details →
1.3.1 13 May 2013 C3 H1 MIT Yes Details →
1.3.0 13 May 2013 C3 H1 MIT Yes Details →
1.2.0 13 May 2013 C3 H1 MIT Yes Details →
1.1.0 13 May 2013 C3 H1 MIT Yes Details →
1.0.0 13 May 2013 C2 H1 MIT Yes Details →
0.1.1 17 Apr 2013 C2 H1 MIT Yes Details →
0.1.0 15 Apr 2013 C2 H1 MIT Yes Details →
0.0.1 18 May 2012 C2 H1 MIT Yes Details →
0.0.0 18 May 2012 C2 H1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2022 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for shell-quote

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-10541: Potential Command Injection in shell-quote 9.8 critical 1.6.1 18 Feb 2019
CVE-2021-42740: Command Injection in shell-quote 9.8 critical 1.7.3 24 May 2022
CVE-2026-9277: shell-quote Package Vulnerability - Shell Command Injection Risk 8.1 critical 1.8.4 09 Jun 2026
CVE-2026-102422: shell-quote Command Injection via Line Terminator in Comment Token 8.1 critical 1.11.0 06 Oct 2026
CVE-2026-13311: shell-quote Package Suffers from Quadratic-complexity Denial of Service Vulnerability 7.5 high 1.9.0 20 Jul 2026

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 shell-quote

Is shell-quote safe to use?

Vulert records 5 vulnerabilities for shell-quote in npm: 4 critical, 1 high, 0 medium and 0 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 shell-quote's Vulert package health score?

Vulert scores shell-quote 69/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 shell-quote affected?

No. 1.12.0, 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 shell-quote should I use?

1.12.0 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 shell-quote have?

5 vulnerabilities are recorded for shell-quote in the npm ecosystem: 4 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new shell-quote vulnerabilities disclosed?

3 vulnerabilities were recorded for shell-quote in the last 12 months, and the oldest entry in this database dates to 18 Feb 2019. 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 shell-quote 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 shell-quote for upcoming vulnerabilities?

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