CVE-2026-25155 Qwik City CSRF protection middleware does not work properly for content type header with parameters (eg. multipart/form-data)
Attackers can bypass CSRF protection in Qwik applications by exploiting a regex typo in Content-Type header parsing, allowing unauthorized state-changing requests.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-25155?
CVE-2026-25155 is a medium-severity vulnerability in QwikDev qwik, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Qwik is a performance focused javascript framework. Prior to version 1.12.0, a typo in the regular expression within isContentType causes incorrect parsing of certain Content-Type headers. This issue has been patched in version 1.12.0.
Weakness: CWE-352
Which versions are affected by CVE-2026-25155?
2 open source packages ship an affected version, including @builder.io/qwik-city. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
@builder.io/qwik-city npm | All versions | 1.12.0 |
@builder.io/qwik-city npm | All versions | 1.12.0 |
Products include Qwik Qwik.
How do I fix CVE-2026-25155?
Upgrade @builder.io/qwik-city to 1.12.0 or later.
Is CVE-2026-25155 being exploited?
There is no known exploitation of CVE-2026-25155 in the wild and no public exploit code.
Other vulnerabilities in QwikDev qwik
- CVE-2023-1283 Code Injection in builderio/qwik
- CVE-2026-25150 Prototype Pollution via FormData Processing in Qwik City
- CVE-2026-27971 Qwik affected by unauthenticated RCE via server$ Deserialization
- CVE-2026-32701 Qwik has array method pollution in FormData processing, allowing type confusion and DoS
- CVE-2024-41677 Cross-site Scripting (XSS) vulnerability due to improper HTML escaping in qwik
Sources
Also known as GHSA-vm6g-8r4h-22x8.