VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

node-qs: vulnerability history, versions and safety

node-qs is a package in the Debian ecosystem. Vulert records 11 vulnerabilities for it across 15 releases, from Oct 2014 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded U11
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
5 in the last 12 months

Most recent disclosure 30 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all node-qs vulnerabilities

Vulert verdict on node-qs i

Updated on 23 Oct 2026

Careful: 5 of the 11 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 11 vulnerabilities on record across 11 years, 5 in the last year.

What to do: Plan around the 5 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 11 over 11 years · 5 in the last year i
  • Latest disclosure 30 Aug 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 5 i

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 holds for node-qs, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 15 of 15 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 2
  • 2018 2
  • 2022 2
  • 2025 1
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for node-qs

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial-of-Service Vulnerability in node-qs 7.5 high 2.2.4-1 31 May 2018
CVE-2022-24999: Vulnerability in qs Package Causes Node Process Hang in Express 7.5 high 6.9.4+ds-1+deb11u1 26 Nov 2022
Denial of Service Vulnerability in Node.js qs Module N/A unrated 2.2.4-1 19 Oct 2014
Denial-of-Service Vulnerability in Node-qs Package: Event Loop Blocking Due to Deeply Nested Objects N/A unrated 2.2.4-1 31 May 2018
Denial of Service Vulnerability in Node.js qs Module - CVE-2014-7191 N/A unrated 2.2.4-1 19 Oct 2014

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 node-qs

Is node-qs safe to use?

Vulert records 11 vulnerabilities for node-qs in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 11 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does node-qs have?

11 vulnerabilities are recorded for node-qs in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 11 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new node-qs vulnerabilities disclosed?

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

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the node-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.