Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY9 SECURITY RECORDS

quasarframework

quasar

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at quasar, but registry activity is not a publisher support boundary.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-106109 6 Oct 2026 quasar: >= 2.7.0, < 2.23.3; app-vite: >= 1.0.0, < 3.3.0 3.3.0. Update reference ↗
CVE-2026-106107 6 Oct 2026 quasar: < 2.23.4; app-vite: < 3.3.0 3.3.0. Update reference ↗
CVE-2026-106106 6 Oct 2026 quasar: < 2.23.3; render-ssr-error: < 2.2.4; app-vite: < 3.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-106105 6 Oct 2026 quasar: < 2.23.3; app-vite: < 3.3.0; cli: < 5.0.4; ssl-certificate: < 2.1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-106104 6 Oct 2026 quasar: < 2.23.3 2.23.3. Update reference ↗
CVE-2026-106103 6 Oct 2026 quasar: < 2.22.0; icongenie: < 6.1.1 6.1.1. Update reference ↗
CVE-2026-106102 6 Oct 2026 quasar: < 2.22.0 2.22.0. Update reference ↗
CVE-2026-106101 6 Oct 2026 quasar: < 2.32.2 2.32.2. Update reference ↗
CVE-2026-73647 13 Aug 2026 < 2.22.0 2.22.0. Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.