<?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://cve.radiocsirt.org</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>Sat, 10 Oct 2026 20:32:44 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-31510</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-31510</link>
      <description>EUVD-2026-31510</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-31510</guid>
    </item>
    <item>
      <title>fkie_cve-2021-41101</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-41101</link>
      <description>&lt;p&gt;wire-server is an open-source back end for Wire, a secure collaboration platform. Before version 2.106.0, the CORS ` Access-Control-Allow-Origin ` header set by `nginz` is set for all subdomains of `.wire.com` (including `wire.com`). This means that if somebody were to find an XSS vector in any of the subdomains, they could use it to talk to the Wire API using the user&amp;#39;s Cookie. A patch does not exist, but a workaround does. To make sure that a compromise of one subdomain does not yield access to the cookie of another, one may limit the `Access-Control-Allow-Origin` header to apps that actually require the cookie (account-pages, team-settings and the webapp).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;wire-server is an open-source back end for Wire, a secure collaboration platform. Before version 2.106.0, the CORS ` Access-Control-Allow-Origin ` header set by `nginz` is set for all subdomains of `.wire.com` (including `wire.com`). This means that if somebody were to find an XSS vector in any of the subdomains, they could use it to talk to the Wire API using the user&amp;#39;s Cookie. A patch does not exist, but a workaround does. To make sure that a compromise of one subdomain does not yield access to the cookie of another, one may limit the `Access-Control-Allow-Origin` header to apps that actually require the cookie (account-pages, team-settings and the webapp).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-41101</guid>
    </item>
    <item>
      <title>gsd-2021-41101</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-41101</link>
      <description>gsd-2021-41101</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-41101</guid>
    </item>
  </channel>
</rss>
