shell-quote vulnerabilities

quote and parse shell commands

Registry
npm
Latest
1.12.0
License
MIT

5 known advisories

The latest version, 1.12.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:npm install shell-quote@1.12.0

Security advisories for shell-quote

  • CriticalGHSA-pqg4-j6r4-53mv6 Oct 2026

    shell-quote: `quote()` command injection via a line terminator in a token after a `{ comment }` token

    Affected
    >=1.8.4 <1.11.0
    Fixed in
    1.11.0
  • HighGHSA-395f-4hp3-45gv20 Jul 2026

    shell-quote: Quadratic-complexity Denial of Service in `parse()` (CWE-407)

    Affected
    <1.9.0
    Fixed in
    1.9.0
  • CriticalGHSA-w7jw-789q-3m8p9 Jun 2026

    shell-quote quote() does not escape newlines in object .op values

    Affected
    >=1.1.0 <1.8.4
    Fixed in
    1.8.4
  • CriticalGHSA-g4rg-993r-mgx724 May 2022

    Improper Neutralization of Special Elements used in a Command in Shell-quote

    Affected
    >=1.6.3 <1.7.3
    Fixed in
    1.7.3
  • CriticalGHSA-qg8p-v9q4-gh3418 Feb 2019

    Potential Command Injection in shell-quote

    Affected
    <1.6.1
    Fixed in
    1.6.1

Which of your client projects still run an old shell-quote?

NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other npm packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.