<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T16:00:13.151493+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-106101</id>
    <title>fkie_cve-2026-106101</title>
    <updated>2026-10-08T16:00:13.168821+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-106101"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-89vp-x45c-52cq</id>
    <title>GHSA-89vp-x45c-52cq — Quasar Framework: DOM Clobbering in Quasar openURL() SafariViewController Integration Causes Client-Side Denial of Serv…</title>
    <updated>2026-10-08T16:00:13.168889+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: quasar</p>
<p>### Summary</p>
<p>A DOM Clobbering vulnerability exists in Quasar's `openURL()` utility when handling the iOS `SafariViewController` bridge.</p>
<p>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 `&lt;a id="SafariViewController"&gt;` can cause the browser to expose that element as `window.SafariViewController`.</p>
<p>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:</p>
<p>```
TypeError: window.SafariViewController.isAvailable is not a function
```</p>
<p>This can cause client-side denial of service and break navigation-related workflows in Quasar applications.</p>
<p>### Details</p>
<p>Quasar provides the `openURL()` utility to open external URLs. On iOS platforms, this utility supports integration with the native `SafariViewController` bridge.</p>
<p>The vulnerable code is located in:</p>
<p>```
ui/src/utils/open-url/open-url.js
````</p>
<p>The affected logic is:</p>
<p>```javascript
if (Platform.is.ios &amp;&amp; window.SafariViewController !== void 0) {
  window.SafariViewController.isAvailable(available =&gt; {
    if (available) {
      window.SafariViewController.show({ url }, noop, reject)
    }
  })
}
````</p>
<p>The issue is that Quasar only verifies that `window.SafariViewController` is not `undefined`. It does not verify whether the value is the e…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-89vp-x45c-52cq"/>
  </entry>
</feed>
