VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

quasar: vulnerability history, versions and safety

quasar is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 111 releases, from Jul 2026 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
4 vulnerabilities recorded C1 H1 M1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 07 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all quasar vulnerabilities

Vulert verdict on quasar 2.35.2 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 2.35.2 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 4 in the last year i
  • Latest disclosure 07 Oct 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 359 packages i
  • Stars 27,201 i
  • OpenSSF scorecard 4/10 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 quasar, 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
2.35.2 19 Oct 2026 none MIT — Details →
2.35.1 12 Oct 2026 none MIT — Details →
2.35.0 07 Oct 2026 none MIT — Details →
2.34.0 29 Sep 2026 none MIT — Details →
2.33.2 23 Sep 2026 none MIT — Details →
2.33.1 22 Sep 2026 none MIT — Details →
2.33.0 17 Sep 2026 none MIT — Details →
2.32.3 14 Sep 2026 none MIT — Details →
2.32.2 11 Sep 2026 none MIT — Details →
2.32.1 11 Sep 2026 L1 MIT Yes Details →
2.32.0 10 Sep 2026 L1 MIT Yes Details →
2.31.0 08 Sep 2026 L1 MIT Yes Details →
2.30.1 07 Sep 2026 L1 MIT Yes Details →
2.30.0 04 Sep 2026 L1 MIT Yes Details →
2.29.0 02 Sep 2026 L1 MIT Yes Details →
2.28.0 28 Aug 2026 L1 MIT Yes Details →
2.27.0 25 Aug 2026 L1 MIT Yes Details →
2.26.0 21 Aug 2026 L1 MIT Yes Details →
2.25.1 18 Aug 2026 L1 MIT Yes Details →
2.25.0 17 Aug 2026 L1 MIT Yes Details →
2.24.0 05 Aug 2026 L1 MIT Yes Details →
2.23.5 03 Aug 2026 L1 MIT Yes Details →
2.23.4 31 Jul 2026 L1 MIT Yes Details →
2.23.3 28 Jul 2026 L1 MIT Yes Details →
2.23.2 27 Jul 2026 H1 L1 MIT Yes Details →
2.23.1 24 Jul 2026 H1 L1 MIT Yes Details →
2.23.0 24 Jul 2026 H1 L1 MIT Yes Details →
2.22.0 21 Jul 2026 H1 L1 MIT Yes Details →
2.21.4 16 Jul 2026 C1 H1 M1 L1 MIT Yes Details →
2.21.3 13 Jul 2026 C1 H1 M1 L1 MIT Yes Details →
2.21.2 10 Jul 2026 C1 H1 M1 L1 MIT Yes Details →
2.21.1 06 Jul 2026 C1 H1 M1 L1 MIT Yes Details →
2.21.0 03 Jul 2026 C1 H1 M1 L1 MIT Yes Details →
2.20.3 02 Jul 2026 C1 H1 M1 L1 MIT Yes Details →
2.20.2 30 Jun 2026 C1 H1 M1 L1 MIT Yes Details →
2.20.1 16 Jun 2026 C1 H1 M1 L1 MIT Yes Details →
2.20.0 11 Jun 2026 C1 H1 M1 L1 MIT Yes Details →
2.19.3 06 Apr 2026 C1 H1 M1 L1 MIT Yes Details →
2.19.2 26 Mar 2026 C1 H1 M1 L1 MIT Yes Details →
2.19.1 24 Mar 2026 C1 H1 M1 L1 MIT Yes Details →
2.19.0 24 Mar 2026 C1 H1 M1 L1 MIT Yes Details →
2.18.7 17 Mar 2026 C1 H1 M1 L1 MIT Yes Details →
2.18.6 13 Nov 2025 C1 H1 M1 L1 MIT Yes Details →
2.18.5 18 Sep 2025 C1 H1 M1 L1 MIT Yes Details →
2.18.4 17 Sep 2025 C1 H1 M1 L1 MIT Yes Details →
2.18.3 16 Sep 2025 C1 H1 M1 L1 MIT Yes Details →
2.18.2 20 Jul 2025 C1 H1 M1 L1 MIT Yes Details →
2.18.1 06 Mar 2025 C1 H1 M1 L1 MIT Yes Details →
2.18.0 01 Mar 2025 C1 H1 M1 L1 MIT Yes Details →
2.17.7 18 Jan 2025 C1 H1 M1 L1 MIT Yes Details →
2.17.6 03 Jan 2025 C1 H1 M1 L1 MIT Yes Details →
2.17.5 14 Dec 2024 C1 H1 M1 L1 MIT Yes Details →
2.17.4 18 Nov 2024 C1 H1 M1 L1 MIT Yes Details →
2.17.3 16 Nov 2024 C1 H1 M1 L1 MIT Yes Details →
2.17.2 06 Nov 2024 C1 H1 M1 L1 MIT Yes Details →
2.17.1 19 Oct 2024 C1 H1 M1 L1 MIT Yes Details →
2.17.0 17 Sep 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.11 06 Sep 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.10 04 Sep 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.9 15 Aug 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.8 07 Aug 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.7 05 Aug 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.6 10 Jul 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.5 03 Jul 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.4 14 May 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.3 13 May 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.2 08 May 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.1 07 May 2024 C1 H1 M1 L1 MIT Yes Details →
2.16.0 06 May 2024 C1 H1 M1 L1 MIT Yes Details →
2.15.4 23 Apr 2024 C1 H1 M1 L1 MIT Yes Details →
2.15.3 18 Apr 2024 C1 H1 M1 L1 MIT Yes Details →
2.15.2 29 Mar 2024 C1 H1 M1 L1 MIT Yes Details →
2.15.1 14 Mar 2024 C1 H1 M1 L1 MIT Yes Details →
2.15.0 12 Mar 2024 C1 H1 M1 L1 MIT Yes Details →
2.14.7 08 Mar 2024 C1 H1 M1 L1 MIT Yes Details →
2.14.6 29 Feb 2024 C1 H1 M1 L1 MIT Yes Details →
2.14.5 20 Feb 2024 C1 H1 M1 L1 MIT Yes Details →
2.14.4 15 Feb 2024 C1 H1 M1 L1 MIT Yes Details →
2.14.3 25 Jan 2024 C1 H1 M1 L1 MIT Yes Details →
2.14.2 18 Dec 2023 C1 H1 M1 L1 MIT Yes Details →
2.14.1 29 Nov 2023 C1 H1 M1 L1 MIT Yes Details →
2.14.0 13 Nov 2023 C1 H1 M1 L1 MIT Yes Details →
2.13.1 09 Nov 2023 C1 H1 M1 L1 MIT Yes Details →
2.13.0 17 Oct 2023 C1 H1 M1 L1 MIT Yes Details →
2.12.7 13 Sep 2023 C1 H1 M1 L1 MIT Yes Details →
2.12.6 02 Sep 2023 C1 H1 M1 L1 MIT Yes Details →
2.12.5 18 Aug 2023 C1 H1 M1 L1 MIT Yes Details →
2.12.4 07 Aug 2023 C1 H1 M1 L1 MIT Yes Details →
2.12.3 18 Jul 2023 C1 H1 M1 L1 MIT Yes Details →
2.12.2 01 Jul 2023 C1 H1 M1 L1 MIT Yes Details →
2.12.1 28 Jun 2023 C1 H1 M1 L1 MIT Yes Details →
2.12.0 05 May 2023 C1 H1 M1 L1 MIT Yes Details →
1.22.10 05 May 2023 C1 H1 M1 L1 MIT Yes Details →
2.11.10 03 Apr 2023 C1 H1 M1 L1 MIT Yes Details →
1.22.9 03 Apr 2023 C1 H1 M1 L1 MIT Yes Details →
2.11.9 24 Mar 2023 C1 H1 M1 L1 MIT Yes Details →
2.11.8 17 Mar 2023 C1 H1 M1 L1 MIT Yes Details →
1.22.8 17 Mar 2023 C1 H1 M1 L1 MIT Yes Details →
1.22.7 17 Mar 2023 C1 H1 M1 L1 MIT Yes Details →
2.11.7 28 Feb 2023 C1 H1 M1 L1 MIT Yes Details →
1.22.6 28 Feb 2023 C1 H1 M1 L1 — Yes Details →
2.11.6 14 Feb 2023 C1 H1 M1 L1 — Yes Details →
2.11.5 11 Jan 2023 C1 H1 M1 L1 — Yes Details →
1.22.5 11 Jan 2023 C1 H1 M1 L1 — Yes Details →
2.11.4 06 Jan 2023 C1 H1 M1 L1 — Yes Details →
1.22.4 06 Jan 2023 C1 H1 M1 L1 — Yes Details →
2.11.3 29 Dec 2022 C1 H1 M1 L1 — Yes Details →
2.11.2 24 Dec 2022 C1 H1 M1 L1 — Yes Details →
2.11.1 18 Dec 2022 C1 H1 M1 L1 — Yes Details →
2.11.0 17 Dec 2022 C1 H1 M1 L1 — Yes Details →
1.22.3 17 Dec 2022 C1 H1 M1 L1 — Yes Details →
2.10.2 14 Nov 2022 C1 H1 M1 L1 — Yes Details →
1.22.2 14 Nov 2022 C1 H1 M1 L1 — Yes Details →
2.10.1 31 Oct 2022 C1 H1 M1 L1 — Yes Details →
1.22.1 31 Oct 2022 C1 H1 M1 L1 — Yes Details →
2.10.0 14 Oct 2022 C1 H1 M1 L1 — Yes Details →
1.22.0 14 Oct 2022 C1 H1 M1 L1 — Yes Details →
2.9.2 05 Oct 2022 C1 H1 M1 L1 — Yes Details →
1.21.1 05 Oct 2022 C1 H1 M1 L1 — Yes Details →
2.9.1 03 Oct 2022 C1 H1 M1 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for quasar

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-106102: Quasar Framework Stored/Reflected XSS via Unescaped SSR Meta Tag Rendering 10.0 critical 2.22.0 07 Oct 2026
CVE-2026-106104: Quasar Framework Super-linear Regex Backtracking Vulnerability 8.7 high 2.23.3 07 Oct 2026
Prototype Pollution Vulnerability in Quasar Package 5.6 medium 2.22.0 24 Jul 2026
CVE-2026-106101: Quasar Framework DOM Clobbering Vulnerability in openURL() Utility 3.1 low 2.32.2 07 Oct 2026

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 quasar

Is quasar safe to use?

Vulert records 4 vulnerabilities for quasar in npm: 1 critical, 1 high, 1 medium and 1 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 quasar's Vulert package health score?

Vulert scores quasar 75/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 quasar affected?

No. 2.35.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.

How many vulnerabilities does quasar have?

4 vulnerabilities are recorded for quasar in the npm ecosystem: 1 critical, 1 high, 1 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new quasar vulnerabilities disclosed?

4 vulnerabilities were recorded for quasar in the last 12 months, and the oldest entry in this database dates to 24 Jul 2026. 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 quasar 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 quasar for upcoming vulnerabilities?

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