Service disruption via bracket-notation arrayLimit bypass
Published Dec 29, 2025 · Updated Dec 29, 2025
Improper input validation in qs before 6.14.1 allows remote attackers to disrupt services through oversized bracket-notation arrays. The bracket-notation branch in lib/parse.js combines each parsed leaf into an array without enforcing the configured arrayLimit. Exploitation requires an application to parse attacker-controlled input with a very high parameterLimit; the default limit caps bracket arrays at 1,000 elements.
Summary
What happened
Improper input validation in qs before 6.14.1 allows remote attackers to disrupt services through oversized bracket-notation arrays. The bracket-notation branch in lib/parse.js combines each parsed leaf into an array without enforcing the configured arrayLimit. Exploitation requires an application to parse attacker-controlled input with a very high parameterLimit; the default limit caps bracket arrays at 1,000 elements.
The record
- CVE
- CVE-2025-15284
- Published
- Dec 29, 2025
- Updated
- Dec 29, 2025
- Vendor
- ljharb
- Product
- qs
- Classifications
- CWE-20, CAPEC-469, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 29, 2025CVE publishedPublication date reported by the CVE source.
- Dec 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 6.14.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream bracket-notation arrayLimit bypass proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo