# CVE-2025-15284: arrayLimit bypass in bracket notation allows DoS via memory exhaustion

Status: published. Published: 2025-12-29. Updated: 2026-11-22.

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.

## Remediation

- fix: The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches. (source: CNA: harborist) — https://github.com/ljharb/qs/commit/3086902ecf7f088d0d1803887643ac6c03d415b9
- fix: qs (npm): OSV reports a fixed version 6.14.1. Check the advisory for supported release branches. (source: OSV GHSA-6rw7-vpxm-498p) — https://github.com/advisories/GHSA-6rw7-vpxm-498p

## Affected products and versions

-  /  (qs): ≥ 0; < 6.14.1 (affected, semver). Source: CNA: harborist
-  / qs (qs): ≥ 0; < 6.14.1 (affected, semver); OSV events: introduced 0; fixed 6.14.1. Source: OSV GHSA-6rw7-vpxm-498p

## Severity and prioritization

- CVSS 4.0: 6.3 (medium); CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L; source: CNA: harborist

- CVSS 3.1: 3.7 (low); CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L; source: CNA: harborist

- CISA KEV: No listing in collected sources

- EPSS: 0.45% as of 2026-11-22; percentile 39.86%

- SSVC: exploitation none; automatable yes; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-20

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/ljharb/qs/security/advisories/GHSA-6rw7-vpxm-498p (CNA: harborist; vendor-advisory)

- https://github.com/ljharb/qs/commit/3086902ecf7f088d0d1803887643ac6c03d415b9 (CNA: harborist; patch)

- https://github.com/advisories/GHSA-6rw7-vpxm-498p (OSV / GitHub Security Advisories; advisory)

- https://osv.dev/vulnerability/GHSA-6rw7-vpxm-498p (OSV / GitHub Security Advisories; osv)

## Provenance

- CNA: harborist: https://www.cve.org/CVERecord?id=CVE-2025-15284; retrieved 2026-11-22; source updated 2026-11-22

- OSV / GitHub Security Advisories: https://osv.dev/vulnerability/GHSA-6rw7-vpxm-498p; retrieved 2026-11-22; source updated 2026-09-10

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2025-15284; retrieved 2026-11-22; source updated Not reported

Revision: d4fb94f197349c5d2b8d56725cdb8815f1c2d220bd97ce4002a4d09cdbe57440

Canonical: https://y2.dev/cve/CVE-2025-15284

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.