All vulnerabilities

npm

CVE-2026-82417

qs: Denial of Service via Attacker Controlled isBuffer

Severity
Medium 5.3
Published
2 Sept 2026
Last changed
10 Sept 2026
Added to UpHeron
22 Oct 2026
Fixed in
6.16.0
Exploit chance
0.4% in the next 30 daysHigher than 34% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Uncaught exception (CWE-248)Improper handling of exceptional conditions (CWE-703)
Attack
Over the network · No login needed · No user action needed
Attacker can
Slow it down
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Also known as
GHSA-4mjr-xmp4-gh2g
Sources
OSV.dev and GitHub

Description

qs.stringify() calls utils.isBuffer() on every value it serializes, and utils.isBuffer() invokes obj.constructor.isBuffer(obj) without checking that it is callable. A value whose own constructor.isBuffer is a non-function makes qs call a non-callable and throw TypeError. Such a value is produced by qs.parse itself from an untrusted query string when plainObjects: true or allowPrototypes: true is set, so a pure-qs parse → stringify round-trip — no JSON.parse — turns an unauthenticated query string into an uncaught throw.

An attacker-controlled parse input reaches the host application's availability asset — via qs's own recommended plainObjects mitigation — and triggers an uncaught exception during a parse → stringify round-trip.

utils.isBuffer runs at lib/stringify.js:127 for every serialized value:

utils.isBuffer (lib/utils.js:327-333) invokes obj.constructor.isBuffer without verifying it is callable:

From the GitHub Advisory Database, CC BY 4.0. Shortened; the full text is there.

Affected software

SoftwareAffected versions
qsnpm · osv:npm:qs
  • From 2.2.5 before 6.16.0

About qs

Weekly downloads (npm)
262,943,056npm, 15 Nov 2026

References