Qwik is a performance-focused JavaScript framework. Prior to @builder.io/qwik 1.20.0 and @qwik.dev/core 2.0.0-beta.37, default server-side qwik-json deserialization causes ResourceSerializer.$fill$ to pass resource._resolved to Promise.resolve without first rejecting attacker-controlled thenables. An unauthenticated request can provide a plain object whose then property is a QRL for an unregistered symbol, causing an orphaned asynchronous rejection that terminates Node.js under its default unhandled-rejection policy. A single request can crash a server, and repeated requests can keep replicas unavailable. This issue is fixed in @builder.io/qwik 1.20.0 and @qwik.dev/core 2.0.0-beta.37.
CVE-2026-84994
HIGHPre-NVD 8.78.7Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-99978 (ENISA EUVD) · GHSA-x586-xvc8-g7q6 (GitHub Security Advisories)Source: ENISA EUVD
8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.7Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.7
- EG Score
- 8.7HIGHmedium confidence
- EG Risk
- 54EG Risk 54/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity87% × 45%Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.5% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.5%
- EPSS %ILE
- 44th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 13, 2026
Last Modified
October 14, 2026
Advisory Details (3)
Auto-updated Oct 14, 2026Patch available. Sources: github_commit, github, github_pr.
GitHub commit Patch Available
commit c1e7444402f9 (QwikDev/qwik)
Patch available: QwikDev/qwik @qwik.dev/router@2.0.0-beta.47 (contains commit c1e7444402f9)
https://github.com/QwikDev/qwik/commit/c1e7444402f9592b5cf9096e10bf303ab4640511GitHub pull request Patch Available
feat(qwik-city): more info for unhandled exceptions
Patch available: QwikDev/qwik @qwik.dev/router@2.0.0-beta.47 (PR #8655 merged 2026-05-21)
https://github.com/QwikDev/qwik/pull/8655GitHub advisoryMentions a patch (unverified)
Crashing any Qwik Server via Resource thenable · Advisory · QwikDev/qwik · GitHub
https://github.com/QwikDev/qwik/security/advisories/GHSA-x586-xvc8-g7q6Vendor Advisories for CVE-2026-84994(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | @builder.io/qwik @ 1.20.0 (fixes < 1.20.0) | — | ghsa |
| npm | @qwik.dev/core @ 2.0.0-beta37 (fixes < 2.0.0-beta37) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 1 ecosystem)
npm(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| @builder.io/qwik | — |
| — |
| @qwik.dev/core | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 29× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-01 07:38 UTCGHSA enrichmentGHSA-x586-xvc8-g7q6 · GitHub severity HIGH
- 2026-11-01 07:38 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-27 21:10 UTCEG score recompute
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-25 13:55 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-20 17:59 UTCEG score recompute
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-18 03:06 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-14 17:31 UTCEG score recompute
Show 4 moreShow fewer
- 2026-10-14 16:46 UTCEG score recompute
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-13 19:29 UTCEG score recomputeFirst assessed: 8.7 HIGH
- 2026-10-13 19:19 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
4 shownnpm:@builder.io/qwik
Frequently asked(5)
What is CVE-2026-84994?
CVE-2026-84994 is a high-severity vulnerability; its CVE record was published on October 13, 2026. Qwik is a performance-focused JavaScript framework. Prior to @builder.io/qwik 1.20.0 and @qwik.dev/core 2.0.0-beta.37, default server-side qwik-json deserialization causes ResourceSerializer.$fill$ to pass resource._resolved to Promise.resolve without first rejecting attacker-controlled thenables.…
When was the CVE record for CVE-2026-84994 published?
The CVE record for CVE-2026-84994 was published on October 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-84994 actively exploited?
CVE-2026-84994 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84994?
CVE-2026-84994 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-84994?
A fix for CVE-2026-84994 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-84994 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84994
Is Your Infrastructure Affected by CVE-2026-84994?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.