Improper Input Validation vulnerability in qs (parse modules) allows HTTP DoS.This issue affects qs: < 6.14.1.
Summary
The arrayLimit option in qs did not enforce limits for bracket notation (a[]=1&a[]=2), only for indexed notation (a[0]=1). This is a consistency bug; arrayLimit should apply uniformly across all array notations.
Note: The default parameterLimit of 1000 effectively mitigates the DoS scenario originally described. With default options, bracket notation cannot produce arrays larger than parameterLimit regardless of arrayLimit, because each a[]=valueconsumes one parameter slot. The severity has been reduced accordingly.
Details
The arrayLimit option only checked limits for indexed notation (a[0]=1&a[1]=2) but did not enforce it for bracket notation (a[]=1&a[]=2).
Vulnerable code (lib/parse.js:159-162):
if (root === '[]' && options.parseArrays) { obj = utils.combine([], leaf); // No arrayLimit check }
Working code (lib/parse.js:175):
else if (index <= options.arrayLimit) { // Limit checked here obj = []; obj[index] = leaf; }
The bracket notation handler at line 159 uses utils.combine([], leaf) without validating against options.arrayLimit, while indexed notation at line 175 checks index <= options.arrayLimit before creating arrays.
PoC
const qs = require('qs'); const result = qs.parse('a[]=1&a[]=2&a[]=3&a[]=4&a[]=5&a[]=6', { arrayLimit: 5 }); console.log(result.a.length); // Output: 6 (should be max 5)
Note on parameterLimit interaction: The original advisory's "DoS demonstration" claimed a length of 10,000, but parameterLimit (default: 1000) caps parsing to 1,000 parameters. With default options, the actual output is 1,000, not 10,000.
Impact
Consistency bug in arrayLimit enforcement. With default parameterLimit, the practical DoS risk is negligible since parameterLimit already caps the total number of parsed parameters (and thus array elements from bracket notation). The risk increases only when parameterLimit is explicitly set to a very high value.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alma_linux | — | Upgrade sgx-pckid-toolUpgrade sgx-pccsUpgrade sgx-commonUpgrade tdx-qgsUpgrade sgx-pccs-adminUpgrade sgx-mpaUpgrade sgx-libs | May 27, 2026 | May 19, 2026 |
| Atlassian Jira | — | Upgrade to the latest version of Atlassian JIRA | Jan 21, 2026 | Jan 20, 2026 |
| Red Hat Jboss Eap | — | — | Jan 5, 2026 | Dec 29, 2025 |
| Redhat_linux | — | Upgrade sgx-pccsUpgrade tdx-qgs-debuginfoUpgrade sgx-libsUpgrade linux-sgx-debugsourceUpgrade sgx-mpaUpgrade tdx-attest-libs-debuginfoUpgrade sgx-libs-debuginfoUpgrade sgx-pckid-toolUpgrade sgx-pccs-debuginfoUpgrade sgx-pckid-tool-debuginfoUpgrade sgx-mpa-debuginfoUpgrade sgx-commonUpgrade tdx-qgsUpgrade sgx-pccs-adminUpgrade sgx-enclave-devel-debuginfoUpgrade linux-sgx-debuginfo | May 20, 2026 | Dec 29, 2025 |
| Rocky_linux | — | Upgrade linux-sgx-debugsourceUpgrade sgx-pccs-adminUpgrade sgx-mpaUpgrade sgx-libsUpgrade sgx-pccs-debuginfoUpgrade tdx-qgsUpgrade linux-sgx-debuginfoUpgrade tdx-qgs-debuginfoUpgrade sgx-pccsUpgrade sgx-pckid-toolUpgrade sgx-commonUpgrade sgx-pckid-tool-debuginfoUpgrade sgx-libs-debuginfoUpgrade sgx-mpa-debuginfo | Jun 1, 2026 | May 28, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub