CVE-2026-25155
Regular Expression Parsing Flaw in Qwik Framework Content-Type Headers
Publication date: 2026-02-03
Last updated on: 2026-02-10
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| qwik | qwik | to 1.12.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Qwik JavaScript framework prior to version 1.12.0. It is caused by a typo in the regular expression used within the isContentType function, which leads to incorrect parsing of certain Content-Type headers.
How can this vulnerability impact me? :
Because the vulnerability causes incorrect parsing of Content-Type headers, it can lead to improper handling of content types in applications using affected versions of Qwik. This may result in security issues such as improper input validation or processing, potentially allowing attackers to exploit the application.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade the Qwik framework to version 1.12.0 or later, where the issue with the incorrect parsing of certain Content-Type headers has been patched.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know