Description
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.
Recommendation
Update the @qwik.dev/core package to the latest compatible version. Followings are version details:
- Affected version(s): < 2.0.0-beta37
- Patched version(s): 2.0.0-beta37
References
Could your website be exposed too?
SmartScanner can check your website for Qwik: Crashing any Qwik Server via Resource thenable and gives you actionable findings to investigate.
Start a free scanRelated Issues
- Electerm Security Vulnerability: RCE via malicious SSH server filename in openFileWithEditor - CVE-2026-43943
- @angular/router: Denial of Service via Unmatched Empty-Path Outlet Route Matching in Server-Side Rendering (SSR) - CVE-2026-111752
- @angular/router: Denial of Service via RouterLink Query Parameter Retention in Server-Side Rendering (SSR) - CVE-2026-111751
- SQL Injection via unsanitized JSON path keys when ignoring/silencing compilation errors or using `Kysely<any>`. - CVE-2026-32763
You might also like:
See something that needs correcting? Let us knowUpdated October 15, 2026