CVE-2026-32701: Qwik City has array method pollution in FormData processing allows type confusion and DoS
Summary Qwik City improperly inferred arrays from dotted form field names during FormData parsing. By submitting mixed array-index and object-property keys for the same path, an attacker could cause user-controlled properties to be written onto values that application code expected to be arrays.
Published Mar 20, 2026
Affected packages
@builder.io/qwik-city
- Ecosystem
- npm
- Affected
- < 1.19.2
- Fixed in
- 1.19.2
- Check
npm ls @builder.io/qwik-city
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Qwik City improperly inferred arrays from dotted form field names during FormData parsing. By submitting mixed array-index and object-property keys for the same path, an attacker could cause user-controlled properties to be written onto values that application code expected to be arrays.
Description
When processing application/x-www-form-urlencoded or multipart/form-data requests, Qwik City converted dotted field names such as items.0 and items.1 into nested structures. If a path was interpreted as an array, additional attacker-controlled keys on the same path, such as items.toString, items.push, items.valueOf, or items.length, could alter the resulting server-side value in unexpected ways.
Applications that assumed these parsed values were safe arrays could be affected. Depending on application behavior, this could lead to request handling failures, denial of service through malformed array state or oversized lengths, and type confusion in downstream code.
This issue affects form parsing in Qwik City request handling. It does not require authentication if the vulnerable route is publicly reachable.
Impact
An attacker can send crafted form submissions that cause parsed input to differ from the application’s expected shape. Possible outcomes include:
- Triggering runtime errors when application code calls array methods on attacker-influenced values
- Inflating array length or otherwise creating malformed structures that increase server work or memory use
- Causing type confusion in application logic that trusts parsed form data to be a normal array
There is no direct evidence that this issue enables confidentiality or integrity impact by itself; the primary risk is denial of service and application instability.
Patched Versions
Patched in 1.19.2.
Workarounds
Until patched, avoid trusting parsed form data to be a well-formed array when using dotted field names, and validate or normalize action input before using array methods or relying on array shape.
Credited to Y4tacker.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-25148
Qwik SSR XSS via Unsafe Virtual Node Serialization
medium5.3Feb 3, 2026CVE-2026-25149
Qwik City Open Redirect via fixTrailingSlash
low2.7Feb 3, 2026CVE-2026-25150
Prototype Pollution via FormData Processing in Qwik City
critical9.3Feb 3, 2026CVE-2026-25151
Qwik City has a CSRF Protection Bypass via Content-Type Header Validation
medium5.9Feb 3, 2026CVE-2026-25155
Qwik City CSRF protection middleware does not work properly for content type header with parameters (eg. multipart/form-data)
medium5.9Feb 3, 2026CVE-2025-53620
Qwik's unhandled exception vulnerabilty can cause server crashes from malicious requests
critical9.2Jul 9, 2025
