CVE-2026-84994
Unauthenticated JSON can crash Node.js servers via Qwik deserialization bug.
WAF coverage: No CWE mapping, and attack is not network-delivered. Patch is the reliable fix.
Also consider: patch
Is CVE-2026-84994 being exploited?
Not confirmed. CVE-2026-84994 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.52% probability of exploitation in the next 30 days.
How severe is CVE-2026-84994?
CVE-2026-84994 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-84994?
Yes. A fix has been recorded for CVE-2026-84994. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84994 affect?
CVE-2026-84994 affects @builder.io/qwik < 1.20.0, @qwik.dev/core < 2.0.0-beta.37, Node.js servers hosting Qwik apps. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84994?
Upgrade to @builder.io/qwik 1.20.0 or @qwik.dev/core 2.0.0-beta.37 immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated HTTP request can trigger unhandled thenable, crashing Node.js process and causing remote DoS/availability loss.
Immediate action required
- affected< 2.0.0-beta37
- affected< 1.20.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.