Skip to main content
Vulnerability Database/CVE-2026-106101

CVE-2026-106101: Quasar Framework XSS Vulnerability

CVE-2026-106101 is a cross-site scripting vulnerability in Quasar Framework that allows attackers to disrupt URL navigation workflows. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-106101 Overview

CVE-2026-106101 is a type confusion vulnerability in Quasar Framework, a Vue.js-based framework for building high-performance user interfaces. Versions prior to 2.32.2 contain a flaw in the openURL() utility located in ui/src/utils/open-url/open-url.js. The utility trusts window.SafariViewController whenever the global exists in an iOS environment. Attacker-controlled HTML rendered through components such as QEditor, QSelect, or QChatMessage can inject a named SafariViewController element, triggering browser named-property resolution to replace the expected native bridge object. The resulting TypeError disrupts external navigation, login redirects, and payment redirects. The issue is categorized as [CWE-843: Access of Resource Using Incompatible Type (Type Confusion)].

Critical Impact

Attacker-injected HTML on iOS causes openURL() to throw a TypeError, breaking login, payment, and external navigation workflows in affected Quasar applications.

Affected Products

  • Quasar Framework versions prior to 2.32.2
  • Applications using QEditor with attacker-controlled HTML input
  • Applications using QSelect or QChatMessage configured for HTML rendering

Discovery Timeline

  • 2026-10-06 - CVE-2026-106101 published to NVD
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-106101

Vulnerability Analysis

The openURL() utility in Quasar Framework determines whether to use the native iOS SafariViewController bridge by checking the global window.SafariViewController. The pre-patch logic only verified that the property was not undefined before invoking isAvailable() on it. This assumption fails because browsers expose named HTML elements as properties of window through named-property resolution. An attacker who injects HTML containing an element named SafariViewController (for example, <a name="SafariViewController">) replaces the expected native bridge object with a DOM element reference. When application code subsequently calls openURL(), the engine invokes isAvailable() on an HTML element that has no such method, producing an uncaught TypeError and breaking URL-opening workflows.

Root Cause

The root cause is unsafe duck-typing of a global binding. Quasar inferred the presence of a native bridge from existence of a property name alone, without validating that the resolved value exposed the expected methods. This pattern is vulnerable to DOM clobbering whenever any component renders attacker-controlled HTML.

Attack Vector

Exploitation requires an application to render attacker-controlled HTML through a Quasar component configured for HTML output, such as QEditor, QSelect with HTML rendering, or QChatMessage with HTML content. The attacker supplies HTML that defines a named element. On an iOS browser context, any later call to openURL() resolves window.SafariViewController to the DOM node and throws when calling isAvailable(). The impact is limited to availability of URL-opening functionality; no code execution or data disclosure results.

javascript
// Patch in ui/src/utils/open-url/open-url.js
export default function openUrl(url, reject, windowFeatures) {
-  if (Platform.is.ios && window.SafariViewController !== void 0) {
-    window.SafariViewController.isAvailable(available => {
+  const safariViewController = window.SafariViewController
+
+  if (
+    Platform.is.ios &&
+    typeof safariViewController?.isAvailable === 'function' &&
+    typeof safariViewController.show === 'function'
+  ) {
+    safariViewController.isAvailable(available => {
       if (available) {
-        window.SafariViewController.show({ url }, noop, reject)
+        safariViewController.show({ url }, noop, reject)
       } else {
         openWindow(url, reject, windowFeatures)
       }

Source: Quasar Framework patch commit 52d874b. The fix captures the global into a local variable and validates that both isAvailable and show are functions before invocation.

Detection Methods for CVE-2026-106101

Indicators of Compromise

  • Uncaught TypeError entries in client-side telemetry referencing SafariViewController.isAvailable is not a function on iOS user agents
  • User-submitted HTML content containing elements with name="SafariViewController" or id="SafariViewController"
  • Failed login redirects, payment redirects, or external navigation events originating from iOS sessions

Detection Strategies

  • Audit application dependencies for Quasar Framework versions below 2.32.2 using npm ls quasar or equivalent package tooling
  • Scan stored user-generated content for HTML attributes that could clobber global JavaScript bindings, specifically named elements matching known browser bridge identifiers
  • Review usage of QEditor, QSelect, and QChatMessage components for configurations that render raw HTML without sanitization

Monitoring Recommendations

  • Capture client-side JavaScript exceptions through a Real User Monitoring (RUM) or error-tracking service and alert on spikes of TypeError events on iOS user agents
  • Monitor web application firewall logs for POST payloads containing suspicious HTML attributes targeting named-property clobbering
  • Track completion rates for authentication and payment flows segmented by platform to identify iOS-specific regressions

How to Mitigate CVE-2026-106101

Immediate Actions Required

  • Upgrade Quasar Framework to version 2.32.2 or later in all affected applications
  • Sanitize user-supplied HTML rendered through QEditor, QSelect, and QChatMessage using an allowlist-based sanitizer such as DOMPurify
  • Audit application code for other instances where globals are duck-typed by existence rather than by method signature validation

Patch Information

The fix is published in Quasar Framework Release v2.32.2 and tracked under GitHub Security Advisory GHSA-89vp-x45c-52cq. The patch validates that SafariViewController.isAvailable and SafariViewController.show are both functions before invocation, neutralizing DOM-clobbering substitution.

Workarounds

  • Disable HTML rendering in QSelect and QChatMessage components until the upgrade is applied
  • Strip or escape name and id attributes from attacker-controlled HTML before storage or rendering
  • Wrap calls to openURL() in try/catch blocks to prevent uncaught exceptions from breaking downstream workflows
bash
# Upgrade Quasar Framework to the patched release
npm install quasar@2.32.2

# Verify installed version
npm ls quasar

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.