<?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>Sun, 04 Oct 2026 17:13:40 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-191994</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-191994</link>
      <description>EUVD-2026-191994</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-191994</guid>
    </item>
    <item>
      <title>fkie_cve-2023-39520</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-39520</link>
      <description>&lt;p&gt;Cryptomator encrypts data being stored on cloud infrastructure. The MSI installer provided on the homepage for Cryptomator version 1.9.2 allows local privilege escalation for low privileged users, via the `repair` function. The problem occurs as the repair function of the MSI is spawning an SYSTEM Powershell without the `-NoProfile` parameter. Therefore the profile of the user starting the repair will be loaded. Version 1.9.3 contains a fix for this issue. Adding a `-NoProfile` to the powershell is a possible workaround.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Cryptomator encrypts data being stored on cloud infrastructure. The MSI installer provided on the homepage for Cryptomator version 1.9.2 allows local privilege escalation for low privileged users, via the `repair` function. The problem occurs as the repair function of the MSI is spawning an SYSTEM Powershell without the `-NoProfile` parameter. Therefore the profile of the user starting the repair will be loaded. Version 1.9.3 contains a fix for this issue. Adding a `-NoProfile` to the powershell is a possible workaround.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-39520</guid>
    </item>
    <item>
      <title>gsd-2023-39520</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-39520</link>
      <description>gsd-2023-39520</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-39520</guid>
    </item>
  </channel>
</rss>
