Advisory record · GHSA-pq96-jpmf-w254

Quasar Framework: Stored/Reflected XSS via unescaped SSR meta tag rendering in getHead()

CVSS 10.0 CriticalCriticalEPSS 0.0030 · 22nd percentile

Critical, because:

  • CVSS score 10.0: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 7 Oct 2026, 16:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
quasarnpm<2.22.02.22.0
Identifiers
GHSA-pq96-jpmf-w254 · CVE-2026-106102
Weakness (CWE)
CWE-79 · CWE-116
Published
7 Oct 2026
Updated
7 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Quasar framework versions before 2.22.0 render page title and meta/link/script tag values into server-side HTML without escaping, so text passed to useMeta() can break out of its tag and inject markup, including scripts. An attacker who can influence that text, such as a blog title or a user display name, can get script to run in the origin of every visitor to the affected page, with no authentication required. Upgrade the quasar package to version 2.22.0 or later.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
10.0 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0030, the 22nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:33 UTC First seen by agentprime
  2. 31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.