p PatchFirst

CVE-2026-2391

CVE-2026-2391 · qs's arrayLimit bypass in comma parsing allows denial of service

This page contains facts from public vulnerability sources. Check the original advisory before updating.

### 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.

CVSS 6.3 · Medium · EPSS 0.5% · Fix available

Published
Updated

Stack: system · node

Affected products and versions

  • node-qs Debian:12

    Versions
    • 6.11.0+ds+~6.9.7-3
    • 6.11.0+ds+~6.9.7-4
    • 6.13.0+ds+~6.9.16-1
    • 6.14.1+ds+~6.14.0-1
    • 6.15.0+ds+~6.15.0-1
    • 6.15.0+ds+~6.15.0-2
    • 6.15.0+ds+~6.15.0-3
    • 6.15.2+ds+~6.15.1-1
    • 6.16.0+ds+~6.15.1-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-qs Debian:13

    Versions
    • 6.13.0+ds+~6.9.16-1
    • 6.14.1+ds+~6.14.0-1
    • 6.15.0+ds+~6.15.0-1
    • 6.15.0+ds+~6.15.0-2
    • 6.15.0+ds+~6.15.0-3
    • 6.15.2+ds+~6.15.1-1
    • 6.16.0+ds+~6.15.1-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-qs Debian:14

    Versions
    • 6.13.0+ds+~6.9.16-1
    • 6.14.1+ds+~6.14.0-1
    Affected ranges
    • ECOSYSTEM: < 6.15.0+ds+~6.15.0-1

    Update to 6.15.0+ds+~6.15.0-1

  • qs npm

    Affected ranges
    • SEMVER: ≥ 6.7.0, < 6.14.2

    Update to 6.14.2

  • node-qs Ubuntu:Pro:14.04:LTS

    Versions
    • 0.4.2-1
    • 0.6.5-1
    • 0.6.5-1ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-qs Ubuntu:16.04:LTS

    Versions
    • 2.2.4-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-qs Ubuntu:18.04:LTS

    Versions
    • 2.2.4-1
    • 2.2.4-1ubuntu1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-qs Ubuntu:Pro:20.04:LTS

    Versions
    • 6.5.2-1
    • 6.9.0+ds-1
    • 6.9.1+ds-1
    • 6.9.1+ds-1ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-qs Ubuntu:22.04:LTS

    Versions
    • 6.9.4+ds-1
    • 6.10.1+ds-1
    • 6.10.2+ds+~6.9.7-1
    • 6.10.3+ds+~6.9.7-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-qs Ubuntu:24.04:LTS

    Versions
    • 6.11.0+ds+~6.9.7-3
    • 6.11.0+ds+~6.9.7-4
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-qs Ubuntu:25.10

    Versions
    • 6.13.0+ds+~6.9.16-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-qs Ubuntu:26.10

    Versions
    • 6.14.1+ds+~6.14.0-1
    • 6.15.2+ds+~6.15.1-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-qs Ubuntu:26.04:LTS

    Versions
    • 6.13.0+ds+~6.9.16-1
    • 6.14.1+ds+~6.14.0-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →