VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

qs: vulnerability history, versions and safety

qs is a package in the npm ecosystem. Vulert records 10 vulnerabilities for it across 118 releases, from Oct 2017 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded H6 M3 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
5 in the last 12 months

Most recent disclosure 02 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all qs vulnerabilities

Vulert verdict on qs 6.16.1 i

Updated on 22 Oct 2026

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

Package health score 75/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 6.16.1 — unaffected i
  • Vulnerabilities on record 10 over 8 years · 5 in the last year i
  • Latest disclosure 02 Sep 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 430,071 packages i
  • Stars 8,946 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence BSD-3-Clause i
  • Similar names ws 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 qs, 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
6.16.1 14 Oct 2026 none BSD-3-Clause — Details →
6.16.0 29 Aug 2026 none BSD-3-Clause — Details →
6.15.3 24 Jun 2026 M2 BSD-3-Clause Yes Details →
6.15.2 16 May 2026 M2 BSD-3-Clause Yes Details →
6.15.1 08 Apr 2026 M3 BSD-3-Clause Yes Details →
6.15.0 15 Feb 2026 M3 BSD-3-Clause Yes Details →
6.13.3 13 Feb 2026 H1 M2 L1 BSD-3-Clause Yes Details →
6.12.5 13 Feb 2026 H1 M2 L1 BSD-3-Clause Yes Details →
6.11.4 13 Feb 2026 H1 M2 L1 BSD-3-Clause Yes Details →
6.10.7 13 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.9.9 13 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.8.5 13 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.7.5 13 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.6.3 13 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.5.5 13 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.4.3 13 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.3.5 13 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.2.6 13 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.1.4 13 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.0.6 13 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.0.5 12 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.1.3 12 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.2.5 12 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.3.4 12 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.4.2 12 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.5.4 12 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.6.2 12 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.7.4 12 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.8.4 12 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.9.8 12 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.10.6 12 Feb 2026 H1 M1 L1 BSD-3-Clause Yes Details →
6.11.3 12 Feb 2026 H1 M2 L1 BSD-3-Clause Yes Details →
6.12.4 12 Feb 2026 H1 M2 L1 BSD-3-Clause Yes Details →
6.13.2 12 Feb 2026 H1 M2 L1 BSD-3-Clause Yes Details →
6.14.2 11 Feb 2026 M3 BSD-3-Clause Yes Details →
6.14.1 29 Dec 2025 M2 L1 BSD-3-Clause Yes Details →
6.14.0 14 Jan 2025 H1 M2 L1 BSD-3-Clause Yes Details →
6.13.1 17 Nov 2024 H1 M2 L1 BSD-3-Clause Yes Details →
6.13.0 01 Aug 2024 H1 M2 L1 BSD-3-Clause Yes Details →
6.12.3 08 Jul 2024 H1 M2 L1 BSD-3-Clause Yes Details →
6.12.2 01 Jul 2024 H1 M2 L1 BSD-3-Clause Yes Details →
6.12.1 12 Apr 2024 H1 M2 L1 BSD-3-Clause Yes Details →
6.12.0 06 Mar 2024 H1 M2 L1 BSD-3-Clause Yes Details →
6.11.2 15 May 2023 H1 M2 L1 BSD-3-Clause Yes Details →
6.11.1 06 Mar 2023 H1 M2 L1 BSD-3-Clause Yes Details →
6.11.0 27 Jun 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.10.5 06 Jun 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.10.4 06 Jun 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.10.3 11 Jan 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.9.7 11 Jan 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.8.3 11 Jan 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.7.3 11 Jan 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.6.1 11 Jan 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.5.3 11 Jan 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.4.1 11 Jan 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.3.3 11 Jan 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.2.4 11 Jan 2022 H1 M1 L1 BSD-3-Clause Yes Details →
6.10.2 06 Dec 2021 H2 M1 L1 BSD-3-Clause Yes Details →
6.10.1 22 Mar 2021 H2 M1 L1 BSD-3-Clause Yes Details →
6.10.0 18 Mar 2021 H2 M1 L1 BSD-3-Clause Yes Details →
6.9.6 14 Jan 2021 H1 M1 L1 BSD-3-Clause Yes Details →
6.9.5 13 Jan 2021 H1 M1 L1 BSD-3-Clause Yes Details →
6.9.4 03 May 2020 H1 M1 L1 BSD-3-Clause Yes Details →
6.9.3 25 Mar 2020 H1 M1 L1 BSD-3-Clause Yes Details →
6.8.2 25 Mar 2020 H1 M1 L1 BSD-3-Clause Yes Details →
6.7.2 25 Mar 2020 H1 M1 L1 BSD-3-Clause Yes Details →
6.7.1 24 Mar 2020 H1 M1 L1 BSD-3-Clause Yes Details →
6.8.1 24 Mar 2020 H1 M1 L1 BSD-3-Clause Yes Details →
6.9.2 22 Mar 2020 H1 M1 L1 BSD-3-Clause Yes Details →
6.9.1 08 Nov 2019 H1 M1 L1 BSD-3-Clause Yes Details →
6.9.0 21 Sep 2019 H1 M1 L1 BSD-3-Clause Yes Details →
6.8.0 17 Aug 2019 H1 M1 L1 BSD-3-Clause Yes Details →
6.7.0 22 Mar 2019 H1 M1 L1 BSD-3-Clause Yes Details →
6.6.0 25 Nov 2018 H1 M1 L1 BSD-3-Clause Yes Details →
6.5.2 04 May 2018 H1 M1 L1 BSD-3-Clause Yes Details →
6.5.1 09 Sep 2017 H1 M1 L1 BSD-3-Clause Yes Details →
6.5.0 28 Jun 2017 H1 M1 L1 BSD-3-Clause Yes Details →
6.0.4 06 Mar 2017 H1 M1 L1 BSD-3-Clause Yes Details →
6.1.2 06 Mar 2017 H1 M1 L1 BSD-3-Clause Yes Details →
6.2.3 06 Mar 2017 H1 M1 L1 BSD-3-Clause Yes Details →
6.3.2 06 Mar 2017 H1 M1 L1 BSD-3-Clause Yes Details →
6.4.0 06 Mar 2017 H1 M1 L1 BSD-3-Clause Yes Details →
6.2.2 16 Feb 2017 H1 M1 L1 BSD-3-Clause Yes Details →
6.0.3 16 Feb 2017 H2 M1 L1 BSD-3-Clause Yes Details →
6.1.1 16 Feb 2017 H1 M1 L1 BSD-3-Clause Yes Details →
6.3.1 16 Feb 2017 H1 M1 L1 BSD-3-Clause Yes Details →
6.3.0 17 Oct 2016 H1 M1 L1 BSD-3-Clause Yes Details →
6.2.1 20 Jul 2016 H1 M1 L1 BSD-3-Clause Yes Details →
5.2.1 20 Jul 2016 H2 M1 L1 BSD-3-Clause Yes Details →
6.2.0 08 May 2016 H1 M1 L1 BSD-3-Clause Yes Details →
6.1.0 04 Feb 2016 H1 M1 L1 BSD-3-Clause Yes Details →
6.0.2 17 Jan 2016 H2 M1 L1 BSD-3-Clause Yes Details →
6.0.1 24 Nov 2015 H2 M1 L1 BSD-3-Clause Yes Details →
6.0.0 03 Nov 2015 H2 M1 L1 BSD-3-Clause Yes Details →
5.2.0 07 Oct 2015 H2 M1 L1 BSD-3-Clause Yes Details →
5.1.0 11 Sep 2015 H2 M1 L1 BSD-3-Clause Yes Details →
5.0.0 27 Aug 2015 H2 M1 L1 BSD-3-Clause Yes Details →
4.0.0 02 Jul 2015 H2 M1 L1 BSD-3-Clause Yes Details →
3.1.0 27 May 2015 H2 M1 L1 BSD-3-Clause Yes Details →
3.0.0 22 May 2015 H2 M1 L1 BSD-3-Clause Yes Details →
2.4.2 09 May 2015 H2 M1 L1 — Yes Details →
2.4.1 13 Mar 2015 H2 M1 L1 — Yes Details →
2.4.0 12 Mar 2015 H2 M1 L1 — Yes Details →
2.3.3 14 Nov 2014 H2 M1 L1 — Yes Details →
2.3.2 28 Oct 2014 H2 M1 L1 — Yes Details →
2.3.1 23 Oct 2014 H2 M1 L1 — Yes Details →
2.3.0 22 Oct 2014 H2 M1 L1 — Yes Details →
2.2.5 22 Oct 2014 H2 M1 L1 — Yes Details →
2.2.4 18 Sep 2014 H2 L1 — Yes Details →
2.2.3 05 Sep 2014 H2 L1 — Yes Details →
2.2.2 29 Aug 2014 H2 L1 — Yes Details →
2.2.1 28 Aug 2014 H2 L1 — Yes Details →
2.2.0 27 Aug 2014 H2 L1 — Yes Details →
2.1.0 25 Aug 2014 H2 L1 — Yes Details →
2.0.0 25 Aug 2014 H2 L1 — Yes Details →
1.2.2 14 Aug 2014 H2 L1 — Yes Details →
1.2.1 09 Aug 2014 H2 L1 — Yes Details →
1.2.0 07 Aug 2014 H2 L1 — Yes Details →
1.1.0 06 Aug 2014 H2 L1 — Yes Details →
1.0.2 06 Aug 2014 H2 L1 — Yes Details →

The newest 120 of 151 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 2
  • 2020 1
  • 2022 1
  • 2025 1
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for qs

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-1000048: Prototype Pollution Protection Bypass in qs 7.5 high 6.0.4 30 Apr 2020
CVE-2022-24999: Prototype Pollution in qs 7.5 high 6.10.3 27 Nov 2022
Denial of Service via Memory Exhaustion in qs Package 7.5 high 6.14.1 30 Dec 2025
CVE-2026-8723: qs Package Suffers from TypeError DoS on Null/Undefined Entries 5.3 medium 6.15.2 22 May 2026
CVE-2026-82417: qs Denial of Service via Attacker Controlled isBuffer 5.3 medium 6.16.0 02 Sep 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 qs

Is qs safe to use?

Vulert records 10 vulnerabilities for qs in npm: 0 critical, 6 high, 3 medium and 1 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 qs's Vulert package health score?

Vulert scores qs 75/100, which reads as in good shape. 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 qs affected?

No. 6.16.1, 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.

How many vulnerabilities does qs have?

10 vulnerabilities are recorded for qs in the npm ecosystem: 0 critical, 6 high, 3 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new qs vulnerabilities disclosed?

5 vulnerabilities were recorded for qs in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 qs 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 qs for upcoming vulnerabilities?

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