CVE-2026-25155: Qwik City CSRF Protection Bypass Due to Content-Type Header Parsing Issue
Summary
CVE-2026-25155: A typo in the regular expression within isContentType causes incorrect parsing of certain Content-Type headers. Affects @builder.io/qwik-city versions < 1.12.0. Fixed in 1.12.0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Qwik City is a framework designed for building web applications with a focus on performance and developer experience. It provides features such as server-side rendering, routing, and state management. However, it has a vulnerability in its CSRF protection middleware that can be exploited under certain conditions, particularly when handling Content-Type headers with parameters.
Vulnerability Detail
The vulnerability arises from a typo in the regular expression used in the isContentType function, which leads to incorrect parsing of Content-Type headers like multipart/form-data. This flaw allows attackers to bypass Qwik City's Origin-based CSRF protections, enabling them to perform forged form submissions. As a result, unauthorized state changes can occur, potentially compromising the integrity of the application.
How To Fix
Latest published version: 1.20.2 as of 22 Oct 2026
npm install @builder.io/qwik-city@1.20.2Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.12.0
This is the first release that contains the fix.
npm install @builder.io/qwik-city@1.12.0Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, consider implementing additional validation checks on incoming requests to ensure that they originate from trusted sources. This can help mitigate the risk of CSRF attacks until the package is updated.
Conclusion
In summary, the vulnerability identified as CVE-2026-25155 in the Qwik City framework poses a risk of CSRF attacks due to improper handling of Content-Type headers. It is crucial to update to the patched version to secure your application and consider implementing additional validation as a temporary measure.
See every vulnerability recorded for @builder.io/qwik-city →
FAQ
The vulnerability allows attackers to bypass CSRF protections due to incorrect parsing of Content-Type headers.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
The CVSS score for this vulnerability is 5.9, indicating a moderate level of severity.
Update the @builder.io/qwik-city package to version 1.12.0 or later to patch the vulnerability.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.
References
Related vulnerabilities
Recent vulnerabilities recorded for @builder.io/qwik-city.
