HOMEVULNERABILITIESCVE-2026-2391
LOWPOC

CVE-2026-2391

CWE-20Published: February 12, 2026· Updated: Feb 12, 2026

3.7
CVSS v3.1
EPSS:0.04%probability of exploitation in 30 daysPercentile:11.8th

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

NVD Source

Technical Analysis

CVE-2026-2391 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.

The vulnerability requires no privileges and no user interaction, making it a prime target for automated exploitation campaigns and worm-like propagation.

A proof-of-concept (PoC) exploit exists for CVE-2026-2391. While not yet confirmed in active campaigns, the availability of PoC code increases exploitation risk substantially.

CVSS v3.1 Vector Breakdown

Exploitability
Attack VectorNetwork
Attack ComplexityHigh
Privileges Req.None
User InteractionNone
ScopeUnchanged
Impact
ConfidentialityNone
IntegrityNone
AvailabilityLow
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploit & PoC Resources

POC AVAILABLEProof-of-concept code exists
External links open in a new tab. Always verify in a controlled environment before use.

News & Research Mentioning CVE-2026-2391

Critical Apache HTTP/2 Flaw (CVE-2026-23918) Enables DoS and Potential RCE
The Hacker News· May 5, 2026

The Apache Software Foundation (ASF) has released security updates to address several security vulnerabilities in the HTTP Server, including a severe vulnerability that could potentially lead to remote code execution (RCE). The vulnerability, tracked as CVE-2026-23918 (CVSS score: 8.8), has been described as a case of "double free and possible RCE" in the HTTP/2 protocol handling. This issue [xlite_meta score:53 src:The Hacker News xlite_fp:304e823b9fea82e83cb80715907d2fe02f507406a513a79cdab2ef68af3b0248]

All References (3)

Quick Facts

CVE IDCVE-2026-2391
CVSS Score3.7 / 10
SeverityLOW
WeaknessCWE-20
CISA KEVNo
ExploitPOC
EPSS (30d)0.04%
PublishedFeb 12, 2026

Related CVEs (CWE-20)

Recommended Actions

  • Apply vendor patches immediately
  • Monitor CVE-2026-2391 in threat intel feeds
  • Review IDS/IPS signatures for exploitation attempts
Data sourced from NVD (NIST), CISA KEV, and EPSS (FIRST). Analysis generated by CTIWATCH.COM. CVE data is provided under the NVD usage policy.