CVE-2026-25155: Qwik City CSRF protection middleware does not work properly for content type header with parameters (eg. multipart/form-data)
Summary A typo in the regular expression within isContentType causes incorrect parsing of certain Content-Type headers. Impact An attacker can bypass Qwik City’s Origin-based CSRF protections and perform forged form submissions, potentially causing unauthorized state changes.
Published Feb 3, 2026 · Updated Feb 11, 2026
Affected packages
@builder.io/qwik-city
- Ecosystem
- npm
- Affected
- < 1.12.0
- Fixed in
- 1.12.0
- Check
npm ls @builder.io/qwik-city
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A typo in the regular expression within isContentType causes incorrect parsing of certain Content-Type headers.
Impact
An attacker can bypass Qwik City’s Origin-based CSRF protections and perform forged form submissions, potentially causing unauthorized state changes.
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-32701
Qwik City has array method pollution in FormData processing allows type confusion and DoS
high7.5Mar 20, 2026CVE-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-2025-53620
Qwik's unhandled exception vulnerabilty can cause server crashes from malicious requests
critical9.2Jul 9, 2025
