Qwik is a performance-focused JavaScript framework. Versions prior to 1.19.2 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. When processing application/x-www-form-urlencoded or multipart/form-data requests, Qwik City converted dotted field names (e.g., items.0, items.1) into nested structures. If a path was interpreted as an array, additional attacker-supplied keys on that path—such as items.toString, items.push, items.valueOf, or items.length—could alter the resulting server-side value in unexpected ways, potentially leading to request handling failures, denial of service through malformed array state or oversized lengths, and type confusion in downstream code. This issue was fixed in version 1.19.2.
CVE-2026-32701
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
March 20, 2026
Last Modified
June 17, 2026
References (2)
- security-advisories@githubhttps://github.com/QwikDev/qwik/commit/7b5867c3dd8925df9aa96c4296b1e95a4c2af87d
- security-advisories@githubhttps://github.com/QwikDev/qwik/security/advisories/GHSA-whhv-gg5v-864r
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:35 UTCEG score recompute
- 2026-07-27 14:27 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-843 · CWE-1321
- CVE-2010-2299EG 10.0HIGH
- CVE-2011-10019EG 9.8CRITICAL
- CVE-2016-1000005EG 9.8CRITICAL
- CVE-2016-6992NVD 8.8EG 9.8EPSS p93CRITICAL
- CVE-2012-0507EG 9.8 KEVEPSS p100CRITICAL
- CVE-2012-0752EG 9.3EPSS p95HIGH
- CVE-2017-5070NVD 8.8EG 9.0 KEVEPSS p98CRITICAL
- CVE-2017-11292NVD 8.8EG 9.0 KEVEPSS p96CRITICAL
- CVE-2017-8291NVD 7.8EG 9.0 KEVEPSS p100CRITICAL
- CVE-2017-0037NVD 8.1EG 9.0 KEVEPSS p100CRITICAL
Frequently asked(4)
What is CVE-2026-32701?
When was CVE-2026-32701 disclosed?
What is the CVSS score of CVE-2026-32701?
How do I remediate CVE-2026-32701?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32701
Is Your Infrastructure Affected by CVE-2026-32701?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.