Medium severity · published Feb 3, 2026
CVE-2026-25151
Qwik City has a CSRF Protection Bypass via Content-Type Header Validation
5.9
CVSS
0.2%
EPSS
No
On KEV
Description
Qwik is a performance focused javascript framework. Prior to version 1.19.0, Qwik City’s server-side request handler inconsistently interprets HTTP request headers, which can be abused by a remote attacker to circumvent form submission CSRF protections using specially crafted or multi-valued Content-Type headers. This issue has been patched in version 1.19.0.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Confidentiality
Low
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 8% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
QW
qwik · QwikDev
< 1.19.0 · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-25151
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-25151
Patch
https://github.com/QwikDev/qwik/commit/eebf610e04cc3a690f11e10191d09ff0fca1c7ed
Vendor Advisory
https://github.com/QwikDev/qwik/security/advisories/GHSA-r666-8gjf-4v5f
More from qwik
10.0
CVE-2026-25150
Prototype Pollution via FormData Processing in Qwik City
9.8
CVE-2026-27971
Qwik affected by unauthenticated RCE via server$ Deserialization
8.7
CVE-2026-84994
Qwik: Crashing any Qwik Server via Resource thenable
7.5
CVE-2026-32701
Qwik has array method pollution in FormData processing, allowing type confusion and DoS
7.1
CVE-2026-25155
[qwik-city] CSRF protection middleware does not work properly for content type header with parameters (eg. multipart/form-data)