CVE-2026-2391Disclosure(qs_project / qs)

LOWCVSS 7.5 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch qs_project qs systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

### Summary The `arrayLimit` option in qs does not enforce limits for comma-separated values when `comma: true` is enabled, allowing attackers to cause denial-of-service via memory exhaustion. This is a bypass of the array limit enforcement, similar to the bracket notation bypass addressed in GHSA-6rw7-vpxm-498p (CVE-2025-15284). ### Details When the `comma` option is set to `true` (not the default, but configurable in applications), qs allows parsing comma-separated strings as arrays (e.g., `?param=a,b,c` becomes `['a', 'b', 'c']`). However, the limit check for `arrayLimit` (default: 20) and the optional throwOnLimitExceeded occur after the comma-handling logic in `parseArrayValue`, enabling a bypass. This permits creation of arbitrarily large arrays from a single parameter, leading to excessive memory allocation. **Vulnerable code** (lib/parse.js: lines ~40-50): ```js if (val && typeof val === 'string' && options.comma && val.indexOf(',') > -1) {     return val.split(','); } if (options.throwOnLimitExceeded && currentArrayLength >= options.arrayLimit) {     throw new RangeError('Array limit exceeded. Only ' + options.arrayLimit + ' element' + (options.arrayLimit === 1 ? '' : 's') + ' allowed in an array.'); } return val; ``` The `split(',')` returns the array immediately, skipping the subsequent limit check. Downstream merging via `utils.combine` does not prevent allocation, even if it marks overflows for sparse arrays.This discrepancy allows attackers to send a single parameter with millions of commas (e.g., `?param=,,,,,,,,...`), allocating massive arrays in memory without triggering limits. It bypasses the intent of `arrayLimit`, which is enforced correctly for indexed (`a[0]=`) and bracket (`a[]=`) notations (the latter fixed in v6.14.1 per GHSA-6rw7-vpxm-498p). ### PoC **Test 1 - Basic bypass:** ``` npm install qs ``` ```js const qs = require('qs'); const payload = 'a=' + ','.repeat(25); // 26 elements after split (bypasses arrayLimit: 5) const options = { comma: true, arrayLimit: 5, throwOnLimitExceeded: true }; try {   const result = qs.parse(payload, options);   console.log(result.a.length); // Outputs: 26 (bypass successful) } catch (e) {   console.log('Limit enforced:', e.message); // Not thrown } ``` **Configuration:** - `comma: true` - `arrayLimit: 5` - `throwOnLimitExceeded: true` Expected: Throws "Array limit exceeded" error. Actual: Parses successfully, creating an array of length 26. ### Impact Denial of Service (DoS) via memory exhaustion.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-20

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • qs

Threat summary

  • Patch or workaround signal is available
  • 3 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 3 signals
  • Disclosure: 2 classified signals
  • Peaked 1d ago at 2 mentions (2026-02-12); latest day: 1
  • 3 total mentions across 2 days

Affected systems

Vendors
Products
qs

Deep dive

Activity timeline3 mentions / 2d
01122Mentions · 2026-02-12: 2Mentions · 2026-09-16: 1Patch / Workaround · 2026-09-16: 1Technical Details · 2026-02-12: 2Technical Details · 2026-09-16: 102-1209-16
Signal classification2 categories
Disclosure
266.7%
Patch
133.3%
Referenced assets3 URLs
Classification over time
DateTotalLabels
2026-02-122
Disclosure2
2026-09-161
Patch1
Full discourse3 posts
  • CVE@CVEnew
    Disclosure

    CVE-2026-2391 ### Summary The `arrayLimit` option in qs does not enforce limits for comma-separated values when `comma: true` is enabled, allowing attackers to cause denial-of-servic… https://www.cve.org/CVERecord?id=CVE-2026-2391

    Post summary

    The text announces a denial‑of‑service vulnerability in the qs library where the `arrayLimit` option fails to enforce limits for comma‑separated values when `comma: true` is enabled.

    00010463
    56.5K followersView on X
  • Scout Monitoring@ScoutAPM
    Patch

    Express 5.3.0 fixes CVE-2026-2391: a qs arrayLimit bypass that let arbitrarily large arrays in a query string cause a DoS. Also fixes a Content-Length/Transfer-Encoding header conflict in res.send(). Update if you're on Express. https://github.com/expressjs/express/pull/7468

    Post summary

    The post announces a fix for CVE‑2026‑2391, explaining how a qs array limit bypass leads to DoS and advises upgrading Express to 5.3.0. Specific vulnerability details are given and a patch is available.

    0000086
    1.8K followersView on X
  • cvereports@_cvereports
    Disclosure

    CVE-2026-2391: Death by a Thousand Commas: Deep Dive into CVE-2026-2391 A logic flaw in the popular Node.js `qs` library allows attackers to bypass array limits when the `comma` parsing option is enabled. By sending a crafted query string containing t... https://cvereports.com/reports/CVE-2026-2391

    Post summary

    The article discloses a logic flaw in Node.js's `qs` library that allows bypassing array limits via the comma parsing option, but does not mention exploitation, PoC, or patch.

    0000032
    27 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appqs_projectqs-node.js-

Explore more