Qwik: Crashing any Qwik Server via Resource thenable

高危 8.7CVE-2026-84994 · GHSA-x586-xvc8-g7q6 · Published 13/10/2026 · updated 14/10/2026

要点

CVE-2026-84994 是影响 @builder.io/qwik, @qwik.dev/core 的高危 (CVSS 8.7)漏洞。
未来 30 天内被利用的概率（EPSS）：0.52%，高于 44.5% 的漏洞。
修复：升级到 1.20.0, 2.0.0-beta37 或更高版本。

Package	Affected versions	Patched versions
@builder.io/qwik npm	`< 1.20.0`	`1.20.0`
@qwik.dev/core npm	`< 2.0.0-beta37`	`2.0.0-beta37`

Description

Summary

A Qwik server in the default configuration can be crashed with one unauthenticated HTTP request. During qwik-json body parsing, ResourceSerializer.$fill$ does Promise.resolve(resource._resolved). If _resolved is a plain object whose .then is a QRL for an unregistered symbol, the async QRL rejects, the rejection is orphaned, and Node terminates the process via its default unhandled-rejection policy.

Impact

One unauthenticated request crashes the server. Looping keeps every replica dead as long as the attacker sends requests.

NVD description

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.