<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 16:00:13 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-106101</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-106101</link>
      <description>&lt;p&gt;Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to 2.32.2, the openURL() utility in ui/src/utils/open-url/open-url.js trusted window.SafariViewController whenever that global existed in an iOS environment. Attacker-controlled HTML rendered by components such as QEditor can create a named SafariViewController element, causing browser named-property resolution to replace the expected native bridge object. A later openURL() call then invokes isAvailable() on the element, throws a TypeError, and disrupts external navigation, login redirects, payment redirects, and other URL-opening workflows. QSelect and QChatMessage HTML-rendering configurations can expose the same trigger when they render attacker-controlled HTML. This issue is fixed in version 2.32.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to 2.32.2, the openURL() utility in ui/src/utils/open-url/open-url.js trusted window.SafariViewController whenever that global existed in an iOS environment. Attacker-controlled HTML rendered by components such as QEditor can create a named SafariViewController element, causing browser named-property resolution to replace the expected native bridge object. A later openURL() call then invokes isAvailable() on the element, throws a TypeError, and disrupts external navigation, login redirects, payment redirects, and other URL-opening workflows. QSelect and QChatMessage HTML-rendering configurations can expose the same trigger when they render attacker-controlled HTML. This issue is fixed in version 2.32.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-106101</guid>
    </item>
    <item>
      <title>GHSA-89vp-x45c-52cq — Quasar Framework: DOM Clobbering in Quasar openURL() SafariViewController Integration Causes Client-Side Denial of Serv…</title>
      <link>https://db.gcve.eu/vuln/ghsa-89vp-x45c-52cq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: quasar&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A DOM Clobbering vulnerability exists in Quasar&amp;#39;s `openURL()` utility when handling the iOS `SafariViewController` bridge.&lt;/p&gt;
&lt;p&gt;The vulnerable implementation only checks whether `window.SafariViewController` exists before invoking it as a native bridge object. An attacker who can inject HTML content containing a named element such as `&amp;lt;a id=&amp;#34;SafariViewController&amp;#34;&amp;gt;` can cause the browser to expose that element as `window.SafariViewController`.&lt;/p&gt;
&lt;p&gt;When `openURL()` is later called in an iOS environment, Quasar incorrectly treats the DOM element as the native bridge object and attempts to invoke bridge methods that do not exist, resulting in:&lt;/p&gt;
&lt;p&gt;```
TypeError: window.SafariViewController.isAvailable is not a function
```&lt;/p&gt;
&lt;p&gt;This can cause client-side denial of service and break navigation-related workflows in Quasar applications.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Quasar provides the `openURL()` utility to open external URLs. On iOS platforms, this utility supports integration with the native `SafariViewController` bridge.&lt;/p&gt;
&lt;p&gt;The vulnerable code is located in:&lt;/p&gt;
&lt;p&gt;```
ui/src/utils/open-url/open-url.js
````&lt;/p&gt;
&lt;p&gt;The affected logic is:&lt;/p&gt;
&lt;p&gt;```javascript
if (Platform.is.ios &amp;amp;&amp;amp; window.SafariViewController !== void 0) {
  window.SafariViewController.isAvailable(available =&amp;gt; {
    if (available) {
      window.SafariViewController.show({ url }, noop, reject)
    }
  })
}
````&lt;/p&gt;
&lt;p&gt;The issue is that Quasar only verifies that `window.SafariViewController` is not `undefined`. It does not verify whether the value is the e…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: quasar&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A DOM Clobbering vulnerability exists in Quasar&amp;#39;s `openURL()` utility when handling the iOS `SafariViewController` bridge.&lt;/p&gt;
&lt;p&gt;The vulnerable implementation only checks whether `window.SafariViewController` exists before invoking it as a native bridge object. An attacker who can inject HTML content containing a named element such as `&amp;lt;a id=&amp;#34;SafariViewController&amp;#34;&amp;gt;` can cause the browser to expose that element as `window.SafariViewController`.&lt;/p&gt;
&lt;p&gt;When `openURL()` is later called in an iOS environment, Quasar incorrectly treats the DOM element as the native bridge object and attempts to invoke bridge methods that do not exist, resulting in:&lt;/p&gt;
&lt;p&gt;```
TypeError: window.SafariViewController.isAvailable is not a function
```&lt;/p&gt;
&lt;p&gt;This can cause client-side denial of service and break navigation-related workflows in Quasar applications.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Quasar provides the `openURL()` utility to open external URLs. On iOS platforms, this utility supports integration with the native `SafariViewController` bridge.&lt;/p&gt;
&lt;p&gt;The vulnerable code is located in:&lt;/p&gt;
&lt;p&gt;```
ui/src/utils/open-url/open-url.js
````&lt;/p&gt;
&lt;p&gt;The affected logic is:&lt;/p&gt;
&lt;p&gt;```javascript
if (Platform.is.ios &amp;amp;&amp;amp; window.SafariViewController !== void 0) {
  window.SafariViewController.isAvailable(available =&amp;gt; {
    if (available) {
      window.SafariViewController.show({ url }, noop, reject)
    }
  })
}
````&lt;/p&gt;
&lt;p&gt;The issue is that Quasar only verifies that `window.SafariViewController` is not `undefined`. It does not verify whether the value is the e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-89vp-x45c-52cq</guid>
    </item>
  </channel>
</rss>
