---
id: CVE-2026-106102
title: >-
  Quasar Framework is a framework for building high-performance Vue.js user
  interfaces
summary: >-
  Quasar Framework is a framework for building high-performance Vue.js user
  interfaces. Prior to 2.22.0, the SSR-only getHead() serializer in
  ui/src/plugins/meta/Meta.js used getAttr() to interpolate values supplied
  through useMeta() into …
severity: critical
cvss: 10
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N'
cwe:
  - CWE-79
  - CWE-116
vendor: quasarframework
product: quasar
affected:
  - quasar < 2.22.0
published: '2026-10-06'
updated: '2026-10-06'
sourceUpdated: '2026-10-06T20:03:40.690'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-106102'
references:
  - url: >-
      https://github.com/quasarframework/quasar/commit/11505afe5b5218f2c468f130181815b898fd1e40
    label: security-advisories@github.com
  - url: 'https://github.com/quasarframework/quasar/releases/tag/quasar-v2.22.0'
    label: security-advisories@github.com
  - url: >-
      https://github.com/quasarframework/quasar/security/advisories/GHSA-pq96-jpmf-w254
    label: security-advisories@github.com
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: total
  timestamp: '2026-10-06T17:38:06.088426Z'
ingestedAt: '2026-10-06T18:11:36.223Z'
---

## Overview

Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to 2.22.0, the SSR-only getHead() serializer in ui/src/plugins/meta/Meta.js used getAttr() to interpolate values supplied through useMeta() into title, meta, link, and script markup without HTML text or quoted-attribute encoding. injectServerMeta() appended that output to the raw server-rendered response. An attacker who can influence dynamic page metadata, such as a post title, product name, excerpt, or display name, can terminate the intended HTML context and inject executable markup before hydration. The client-side apply() path is not affected because it uses DOM APIs that encode attributes. This issue is fixed in version 2.22.0.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.