Vulnerability Database · npm · qs · Version
qs 6.7.0
6.7.0 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 1 Medium 1 Low 1 Unrated 0
-
Released 22 Mar 2019
Licence BSD-3-Clause
Also known from other sources 4
Newer releases 151
Database updated 23/Oct/2026
Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version
qs 6.7.0 vulnerabilities
3 vulnerabilities cover qs 6.7.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Denial of Service via Memory Exhaustion in qs Package | 7.5 high | 6.14.1 | 30 Dec 2025 |
| CVE-2026-82417: qs Denial of Service via Attacker Controlled isBuffer | 5.3 medium | 6.16.0 | 02 Sep 2026 |
| CVE-2026-2391: qs Package Array Limit Bypass Leading to Denial of Service | 3.7 low | 6.14.2 | 12 Feb 2026 |
Looking for another version, or everything Vulert holds for qs?
Questions
About qs 6.7.0
Is qs 6.7.0 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover qs 6.7.0: 0 critical, 1 high, 1 medium and 1 low. Each entry above names the fixed version to move to.
Is 6.7.0 the latest release of qs?
No. 6.7.0 was published 22 Mar 2019, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.