dbcve.org
QwikApplication

CVE-2026-25150

CRITICAL · 10.0 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 1.19.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Qwik is a performance focused javascript framework. Prior to version 1.19.0, a prototype pollution vulnerability exists in the formToObj() function within @builder.io/qwik-city middleware. The function processes form field names with dot notation (e.g., user.name) to create nested objects, but fails to sanitize dangerous property names like __proto__, constructor, and prototype. This allows unauthenticated attackers to pollute Object.prototype by sending crafted HTTP POST requests, potentially leading to privilege escalation, authentication bypass, or denial of service. This issue has been patched in version 1.19.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Prototype pollution vulnerability in Qwik City's formToObj() function allows unauthenticated attackers to inject properties into Object.prototype by sending HTTP POST requests with form field names containing dangerous strings like __proto__, constructor, or prototype. This occurs because the function processes dot-notation field names (e.g., user.name) to create nested objects but fails to sanitize these reserved property names.

MitigationUpgrade @builder.io/qwik-city to version 1.19.0 or later which contains the patch for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
QwikApplication
Affected:< 1.19.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Qwik City dependency
    Check your project's package.json or package-lock.json for @builder.io/qwik-city
    Affected if @builder.io/qwik-city is present in dependencies
  2. Check installed version
    Run npm list @builder.io/qwik-city or yarn list @builder.io/qwik-city to see the installed version number
    Affected if The installed version is lower than 1.19.0
  3. Verify formToObj usage
    Search your codebase for imports or usage of formToObj (e.g., grep 'formToObj' or search in your IDE)
    Affected if Your code imports or calls formToObj from @builder.io/qwik-city
  4. Check for form submission endpoints
    Review your route handlers for HTTP POST endpoints that process form data using Qwik City's form handling features
    Affected if Your application accepts POST requests with form data processed by Qwik City form utilities

You are affected if @builder.io/qwik-city version is below 1.19.0 AND your application uses formToObj to process form submissions with user-controlled field names.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.19.0 or later
Fixed in 1.19.0
Vendor patch github.com →
Interim mitigation

Upgrade @builder.io/qwik-city to version 1.19.0 or later which contains the patch for this vulnerability.

Recommended fix High confidence

1.19.0 or latest (>=1.19.0)

  1. Run `npm install @builder.io/[email protected]` or `npm install @builder.io/qwik@latest` to upgrade to the fixed version
  2. Alternatively, run `npm update @builder.io/qwik` to get the latest patch version
  3. Verify the upgrade completed successfully by checking the installed version with `npm list @builder.io/qwik`
  4. Test that the formToObj functionality still works correctly with your application forms after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qwik Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25150 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data