Quick answers
- Is CVE-2026-27971 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-27971 being exploited in the wild.
- How severe is CVE-2026-27971?
- Medium severity, with a CVSS score of 4, published 2 March 2026.
- Which products and versions are affected?
- @builder.io/qwik (npm) SEMVER:introduced=0,fixed=1.19.1.
- Is there a fix for CVE-2026-27971?
- Yes. @builder.io/qwik (npm): upgrade to 1.19.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-27971 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-27971?
- Check whether you run @builder.io/qwik (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @builder.io/qwik (npm): upgrade to 1.19.1 or later
npm install @builder.io/qwik@1.19.1
Technical details
The vulnerability is a CWE-502 unsafe deserialization issue in the server$ RPC mechanism of Qwik versions ≤1.19.0. It allows unauthenticated attackers to execute arbitrary code on the server via a single HTTP request, provided that require() is available at runtime. The attack requires no privileges, no authentication, and minimal attack complexity. Successful exploitation grants remote code execution with full system access (confidentiality, integrity, and availability impact). The vulnerability was patched in version 1.19.1.
Affected products
- Builder.io Qwik <=1.19.0
Identifiers
- CVE-2026-27971
- GHSA-p9x5-jp3h-96mm
Timeline
- 2026-03-02: disclosed
- 2026-03-02: patched: Version 1.19.1 released