VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@builder.io/qwik: vulnerability history, versions and safety

@builder.io/qwik is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 117 releases, from Jan 2023 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C2 H1 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @builder.io/qwik vulnerabilities

Vulert verdict on @builder.io/qwik 1.20.2 i

Updated on 23 Oct 2026

Good news: 1.20.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

What to do: Stay on 1.20.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.20.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.20.2 — unaffected i
  • Vulnerabilities on record 5 over 3 years · 2 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 30 packages i
  • Stars 22,064 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @builder.io/qwik, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.20.2 06 Oct 2026 none MIT — Details →
1.20.1 23 Sep 2026 none MIT — Details →
1.20.0 22 May 2026 none MIT — Details →
1.19.2 13 Mar 2026 H1 MIT Yes Details →
1.19.1 02 Mar 2026 H1 MIT Yes Details →
1.19.0 30 Jan 2026 C1 H1 MIT Yes Details →
1.18.0 17 Dec 2025 C1 H1 MIT Yes Details →
1.17.2 03 Nov 2025 C1 H1 MIT Yes Details →
1.17.1 26 Oct 2025 C1 H1 MIT Yes Details →
1.17.0 08 Oct 2025 C1 H1 MIT Yes Details →
1.16.1 23 Sep 2025 C1 H1 MIT Yes Details →
1.16.0 21 Aug 2025 C1 H1 MIT Yes Details →
1.15.0 21 Jul 2025 C1 H1 MIT Yes Details →
1.14.1 21 May 2025 C1 H1 MIT Yes Details →
1.14.0 21 May 2025 C1 H1 MIT Yes Details →
1.13.0 01 Apr 2025 C1 H1 MIT Yes Details →
1.12.1 20 Feb 2025 C1 H1 MIT Yes Details →
1.12.0 23 Dec 2024 C1 H1 MIT Yes Details →
1.11.0 25 Nov 2024 C1 H1 MIT Yes Details →
1.10.0 11 Nov 2024 C1 H1 MIT Yes Details →
1.9.1 06 Oct 2024 C1 H1 MIT Yes Details →
1.9.0 17 Sep 2024 C1 H1 MIT Yes Details →
1.8.0 08 Aug 2024 C1 H1 MIT Yes Details →
1.7.3 29 Jul 2024 C1 H1 MIT Yes Details →
1.7.2 29 Jul 2024 C1 H1 M1 MIT Yes Details →
1.7.1 11 Jul 2024 C1 H1 M1 MIT Yes Details →
1.7.0-dev20240711122353 11 Jul 2024 C1 H1 M1 MIT Yes Details →
1.7.0 09 Jul 2024 C1 H1 M1 MIT Yes Details →
1.6.0-dev20240709155456 09 Jul 2024 C1 H1 M1 MIT Yes Details →
1.6.0 28 Jun 2024 C1 H1 M1 MIT Yes Details →
1.5.7-dev20240622232308 22 Jun 2024 C1 H1 M1 MIT Yes Details →
1.5.7-dev20240622123737 22 Jun 2024 C1 H1 M1 MIT Yes Details →
1.5.7-dev20240622123731 22 Jun 2024 C1 H1 M1 MIT Yes Details →
1.5.7-dev20240621170050 21 Jun 2024 C1 H1 M1 MIT Yes Details →
1.5.7-dev20240621090019 21 Jun 2024 C1 H1 M1 MIT Yes Details →
1.5.7-dev20240621060015 21 Jun 2024 C1 H1 M1 MIT Yes Details →
1.5.7-dev20240620150612 20 Jun 2024 C1 H1 M1 MIT Yes Details →
1.5.7-dev20240617202805 17 Jun 2024 C1 H1 M1 MIT Yes Details →
1.5.7 12 Jun 2024 C1 H1 M1 MIT Yes Details →
1.5.6 09 Jun 2024 C1 H1 M1 MIT Yes Details →
1.5.5-dev20240528185628 28 May 2024 C1 H1 M1 MIT Yes Details →
1.5.5 21 May 2024 C1 H1 M1 MIT Yes Details →
1.5.4 07 May 2024 C1 H1 M1 MIT Yes Details →
1.5.3-dev20240507162440 07 May 2024 C1 H1 M1 MIT Yes Details →
1.5.3 01 May 2024 C1 H1 M1 MIT Yes Details →
1.5.2-dev20240501181833 01 May 2024 C1 H1 M1 MIT Yes Details →
1.5.2-dev20240424223939 24 Apr 2024 C1 H1 M1 MIT Yes Details →
1.5.2-dev20240423145252 23 Apr 2024 C1 H1 M1 MIT Yes Details →
1.5.2 09 Apr 2024 C1 H1 M1 MIT Yes Details →
1.5.1-dev20240406215013 06 Apr 2024 C1 H1 M1 MIT Yes Details →
1.5.1-dev20240405120538 05 Apr 2024 C1 H1 M1 MIT Yes Details →
1.5.1-dev20240331215559 31 Mar 2024 C1 H1 M1 MIT Yes Details →
1.5.1-dev20240330220902 30 Mar 2024 C1 H1 M1 MIT Yes Details →
1.5.1-dev20240330145203 30 Mar 2024 C1 H1 M1 MIT Yes Details →
1.5.1-dev20240330145200 30 Mar 2024 C1 H1 M1 MIT Yes Details →
1.5.1-dev20240330093502 30 Mar 2024 C1 H1 M1 MIT Yes Details →
1.5.1-dev20240320154426 20 Mar 2024 C1 H1 M1 MIT Yes Details →
1.5.1-dev20240314172558 14 Mar 2024 C1 H1 M1 MIT Yes Details →
1.5.1-dev20240312184808 12 Mar 2024 C1 H1 M1 MIT Yes Details →
1.5.1-dev20240307073646 07 Mar 2024 C1 H1 M1 MIT Yes Details →
1.5.1 06 Mar 2024 C1 H1 M1 MIT Yes Details →
1.5.0-dev20240306115546 06 Mar 2024 C1 H1 M1 MIT Yes Details →
1.5.0 04 Mar 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240304151242 04 Mar 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240304113634 04 Mar 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240304102514 04 Mar 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240303161651 03 Mar 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240301135241 01 Mar 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240301111148 01 Mar 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240229160342 29 Feb 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240229090021 29 Feb 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240229074735 29 Feb 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240228105925 28 Feb 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240224120912 24 Feb 2024 C1 H1 M1 MIT Yes Details →
1.4.5-dev20240223174725 23 Feb 2024 C1 H1 M1 MIT Yes Details →
1.4.5 13 Feb 2024 C1 H1 M1 MIT Yes Details →
1.4.4-dev20240209180746 09 Feb 2024 C1 H1 M1 MIT Yes Details →
1.4.4 06 Feb 2024 C1 H1 M1 MIT Yes Details →
1.4.3-dev20240131062422 31 Jan 2024 C1 H1 M1 MIT Yes Details →
1.4.3-dev20240130172808 30 Jan 2024 C1 H1 M1 MIT Yes Details →
1.4.3 30 Jan 2024 C1 H1 M1 MIT Yes Details →
1.4.2 27 Jan 2024 C1 H1 M1 MIT Yes Details →
1.4.1-dev20240126183013 26 Jan 2024 C1 H1 M1 MIT Yes Details →
1.4.1 25 Jan 2024 C1 H1 M1 MIT Yes Details →
1.4.0-dev20240125130426 25 Jan 2024 C1 H1 M1 MIT Yes Details →
1.4.0-dev20240121214221 21 Jan 2024 C1 H1 M1 MIT Yes Details →
1.4.0 18 Jan 2024 C1 H1 M1 MIT Yes Details →
1.3.5-dev20240118082237 18 Jan 2024 C1 H1 M1 MIT Yes Details →
1.3.5-dev20240117164556 17 Jan 2024 C1 H1 M1 MIT Yes Details →
1.3.5-dev20240117132718 17 Jan 2024 C1 H1 M1 MIT Yes Details →
1.3.5-dev20240116223932 16 Jan 2024 C1 H1 M1 MIT Yes Details →
1.3.5-dev20240116193719 16 Jan 2024 C1 H1 M1 MIT Yes Details →
1.3.5-dev20240115120240 15 Jan 2024 C1 H1 M1 MIT Yes Details →
1.3.5 12 Jan 2024 C1 H1 M1 MIT Yes Details →
1.3.4 11 Jan 2024 C1 H1 M1 MIT Yes Details →
1.3.3 10 Jan 2024 C1 H1 M1 MIT Yes Details →
1.3.2 01 Jan 2024 C1 H1 M1 MIT Yes Details →
1.3.1 15 Dec 2023 C1 H1 M1 MIT Yes Details →
1.3.0 06 Dec 2023 C1 H1 M1 MIT Yes Details →
1.2.19 22 Nov 2023 C1 H1 M1 MIT Yes Details →
1.2.18 16 Nov 2023 C1 H1 M1 — Yes Details →
1.2.17 03 Nov 2023 C1 H1 M1 — Yes Details →
1.2.16 01 Nov 2023 C1 H1 M1 — Yes Details →
1.2.15 26 Oct 2023 C1 H1 M1 — Yes Details →
1.2.14 19 Oct 2023 C1 H1 M1 — Yes Details →
1.2.13 05 Oct 2023 C1 H1 M1 — Yes Details →
1.2.12 18 Sep 2023 C1 H1 M1 — Yes Details →
1.2.11 11 Sep 2023 C1 H1 M1 — Yes Details →
1.2.10 26 Aug 2023 C1 H1 M1 — Yes Details →
1.2.9 25 Aug 2023 C1 H1 M1 — Yes Details →
1.2.8 23 Aug 2023 C1 H1 M1 — Yes Details →
1.2.7 14 Aug 2023 C1 H1 M1 — Yes Details →
1.2.6 06 Jul 2023 C1 H1 M1 — Yes Details →
1.2.5 05 Jul 2023 C1 H1 M1 — Yes Details →
1.2.4 03 Jul 2023 C1 H1 M1 — Yes Details →
1.2.3 30 Jun 2023 C1 H1 M1 — Yes Details →
1.2.2 29 Jun 2023 C1 H1 M1 — Yes Details →
1.2.1 29 Jun 2023 C1 H1 M1 — Yes Details →
1.2.0 29 Jun 2023 C1 H1 M1 — Yes Details →
1.1.5-dev20230625184243 25 Jun 2023 C1 H1 M1 — Yes Details →

The newest 120 of 340 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2
  • 2024 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @builder.io/qwik

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-1283: Code Injection in @builder.io/qwik 9.8 critical 0.21.0 09 Mar 2023
CVE-2026-27971: Qwik Unauthenticated RCE via server$ Deserialization Vulnerability 9.2 critical 1.19.1 02 Mar 2026
CVE-2026-84994: Qwik Server Crash via Resource Thenable 8.7 high 1.20.0 15 Oct 2026
mXSS Vulnerability in @builder.io/qwik 6.3 medium 1.7.3 06 Aug 2024
@builder.io/qwik vulnerable to Cross-site Scripting 6.1 medium 0.16.2 20 Jan 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @builder.io/qwik

Is @builder.io/qwik safe to use?

Vulert records 5 vulnerabilities for @builder.io/qwik in npm: 2 critical, 1 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @builder.io/qwik's Vulert package health score?

Vulert scores @builder.io/qwik 83/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @builder.io/qwik affected?

No. 1.20.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of @builder.io/qwik should I use?

1.20.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @builder.io/qwik have?

5 vulnerabilities are recorded for @builder.io/qwik in the npm ecosystem: 2 critical, 1 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @builder.io/qwik vulnerabilities disclosed?

2 vulnerabilities were recorded for @builder.io/qwik in the last 12 months, and the oldest entry in this database dates to 20 Jan 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @builder.io/qwik are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @builder.io/qwik for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @builder.io/qwik version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.