<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T13:30:06.952611+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/euvd-2026-212300</id>
    <title>EUVD-2026-212300</title>
    <updated>2026-10-04T13:30:07.077305+00:00</updated>
    <content>EUVD-2026-212300</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-212300"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-31134</id>
    <title>fkie_cve-2023-31134</title>
    <updated>2026-10-04T13:30:07.077360+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Tauri is software for building applications for multi-platform deployment. The Tauri IPC is usually strictly isolated from external websites, but in versions 1.0.0 until 1.0.9, 1.1.0 until 1.1.4, and 1.2.0 until 1.2.5, the isolation can be bypassed by redirecting an existing Tauri window to an external website. This is either possible by an application implementing a feature for users to visit
arbitrary websites or due to a bug allowing the open redirect. This allows the external website access to the IPC layer and therefore to all configured and exposed Tauri API endpoints and application specific implemented Tauri commands. This issue has been patched in versions 1.0.9, 1.1.4, and 1.2.5. As a workaround, prevent arbitrary input in redirect features and/or only allow trusted websites access to the IPC.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-31134"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4wm2-cwcf-wwvp</id>
    <title>GHSA-4wm2-cwcf-wwvp — Tauri Open Redirect Vulnerability Possibly Exposes IPC to External Sites</title>
    <updated>2026-10-04T13:30:07.077423+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: tauri</p>
<p>### Impact
The Tauri IPC is usually strictly isolated from external websites but the isolation can be bypassed by redirecting an existing Tauri window to an external website. This is either possible by an application implementing a feature for users to visit arbitrary websites or due to a bug allowing the open redirect[^open-redirect].</p>
<p>This allows the external website access to the IPC layer and therefore to all configured and exposed Tauri API endpoints and application specific implemented Tauri commands.</p>
<p>### Patches
This issue has been patched in the latest release and was backported to all previous `1.x` releases.</p>
<p>### Workarounds
Prevent arbitrary input in redirect features. Only allow trusted websites access to the IPC.</p>
<p>### References</p>
<p>The feature to enable this behavior in a more constrained way was introduced in the `1.3` release and documentation around this can be found in the [documentation](https://tauri.app/v1/api/config/#securityconfig.dangerousremotedomainipcaccess).</p>
<p>[^open-redirect]: [https://en.wikipedia.org/wiki/Open_redirect](https://en.wikipedia.org/wiki/Open_redirect)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4wm2-cwcf-wwvp"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-31134</id>
    <title>gsd-2023-31134</title>
    <updated>2026-10-04T13:30:07.077496+00:00</updated>
    <content>gsd-2023-31134</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-31134"/>
  </entry>
</feed>
