Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Qwik City has array method pollution in FormData processing allows type confusion and DoS

CVE-2026-32701GHSA-whhv-gg5v-864r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@builder.io/qwik-city 1.19.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-32701: 0.44% estimated exploitation activity in the next 30 days; percentile 38.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Qwik City improperly inferred arrays from dotted form field names during FormData parsing. By submitting mixed array-index and object-property keys for the same path, an attacker could cause user-controlled properties to be written onto values that application code expected to be arrays. Description When processing application/x-www-form-urlencoded or multipart/form-data requests, Qwik City converted dotted field names such as items.0 and items.1 into nested structures. If a path was interpreted as an array, additional attacker-controlled keys on the same path, such as items.toString, items.push, items.valueOf, or items.length, could alter the resulting server-side value in unexpected ways. Applications that assumed these parsed values were safe arrays could be affected. Depending on application behavior, this could lead to request handling failures, denial of service through malformed array state or oversized lengths, and type confusion in downstream code. This issue affects…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-whhv-gg5v-864r

  2. Revision 1 · created ·

    Published from osv record GHSA-whhv-gg5v-864r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32701

Advisory: Qwik City has array method pollution in FormData processing allows type confusion and DoS
IDs: CVE-2026-32701, GHSA-whhv-gg5v-864r
Record: https://patchnext.com/advisories/cve-2026-32701 (revision 2, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @builder.io/qwik-city 1.19.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @builder.io/qwik-city: affected < 1.19.2; fixed in 1.19.2

## Suggested inspection (read-only)
- `npm ls @builder.io/qwik-city --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @builder.io/qwik-city.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-whhv-gg5v-864r (OSV record GHSA-whhv-gg5v-864r lists affected ranges: npm @builder.io/qwik-city >=0 <1.19.2 (fixed))
- Verified: https://github.com/advisories/GHSA-whhv-gg5v-864r (GitHub-reviewed advisory GHSA-whhv-gg5v-864r lists affected ranges: npm @builder.io/qwik-city >=0 <1.19.2)

Commands are suggestions: review each one before running it.

Loading voting…