<?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>Thu, 15 Oct 2026 11:29:40 +0000</lastBuildDate>
    <item>
      <title>cnvd-2017-07299</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2017-07299</link>
      <description>cnvd-2017-07299</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2017-07299</guid>
    </item>
    <item>
      <title>EUVD-2026-181934</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-181934</link>
      <description>EUVD-2026-181934</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-181934</guid>
    </item>
    <item>
      <title>fkie_cve-2016-10374</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2016-10374</link>
      <description>&lt;p&gt;perltidy through 20160302, as used by perlcritic, check-all-the-things, and other software, relies on the current working directory for certain output files and does not have a symlink-attack protection mechanism, which allows local users to overwrite arbitrary files by creating a symlink, as demonstrated by creating a perltidy.ERR symlink that the victim cannot delete.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;perltidy through 20160302, as used by perlcritic, check-all-the-things, and other software, relies on the current working directory for certain output files and does not have a symlink-attack protection mechanism, which allows local users to overwrite arbitrary files by creating a symlink, as demonstrated by creating a perltidy.ERR symlink that the victim cannot delete.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2016-10374</guid>
    </item>
    <item>
      <title>GHSA-hxj7-36fx-62r2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hxj7-36fx-62r2</link>
      <description>&lt;p&gt;perltidy through 20160302, as used by perlcritic, check-all-the-things, and other software, relies on the current working directory for certain output files and does not have a symlink-attack protection mechanism, which allows local users to overwrite arbitrary files by creating a symlink, as demonstrated by creating a perltidy.ERR symlink that the victim cannot delete.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;perltidy through 20160302, as used by perlcritic, check-all-the-things, and other software, relies on the current working directory for certain output files and does not have a symlink-attack protection mechanism, which allows local users to overwrite arbitrary files by creating a symlink, as demonstrated by creating a perltidy.ERR symlink that the victim cannot delete.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hxj7-36fx-62r2</guid>
    </item>
    <item>
      <title>gsd-2016-10374</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2016-10374</link>
      <description>gsd-2016-10374</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2016-10374</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2016-10374</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2016-10374</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: perltidy&lt;/p&gt;
&lt;p&gt;perltidy through 20160302, as used by perlcritic, check-all-the-things, and other software, relies on the current working directory for certain output files and does not have a symlink-attack protection mechanism, which allows local users to overwrite arbitrary files by creating a symlink, as demonstrated by creating a perltidy.ERR symlink that the victim cannot delete.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: perltidy&lt;/p&gt;
&lt;p&gt;perltidy through 20160302, as used by perlcritic, check-all-the-things, and other software, relies on the current working directory for certain output files and does not have a symlink-attack protection mechanism, which allows local users to overwrite arbitrary files by creating a symlink, as demonstrated by creating a perltidy.ERR symlink that the victim cannot delete.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2016-10374</guid>
    </item>
  </channel>
</rss>
