Vulnerability in @builder.io/qwik (CVE-2026-84994)
Summary
Vulnerability in @builder.io/qwik (CVE-2026-84994). Risk of unauthorized operations or information disclosure. Exploitable via _resolved. Mitigation: upgrade to 1.20.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-84994 has been found in @builder.io/qwik.
Attackers can target a specific entry point like _resolved over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @builder.io/qwik to 1.20.0 or later.
If unsure, ask your IT team or search "@builder.io/qwik CVE-2026-84994" on the vendor's site.
CVE-2026-84994 (@builder.io/qwik) — CWE-248
Attack surface: _resolved
Patched: 1.20.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-248) exists in @builder.io/qwik. Attackers reach the vulnerable code path via _resolved.
Check the vendor advisory for the affected versions of @builder.io/qwik. Attack surface: _resolved.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.20.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@builder.io/qwik' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@builder.io/qwik' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@builder.io/qwikを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @builder.io/qwik to 1.20.0ステージング環境で 1.20.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。