<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 14:08:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2017-18342</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2017-18342</link>
      <description>&lt;p&gt;In PyYAML before 5.1, the yaml.load() API could execute arbitrary code if used with untrusted data. The load() function has been deprecated in version 5.1 and the &amp;#39;UnsafeLoader&amp;#39; has been introduced for backward compatibility with the function.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In PyYAML before 5.1, the yaml.load() API could execute arbitrary code if used with untrusted data. The load() function has been deprecated in version 5.1 and the &amp;#39;UnsafeLoader&amp;#39; has been introduced for backward compatibility with the function.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2017-18342</guid>
    </item>
    <item>
      <title>GHSA-rprw-h62v-c2w7 — PyYAML insecurely deserializes YAML strings leading to arbitrary code execution</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-rprw-h62v-c2w7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: PyYAML&lt;/p&gt;
&lt;p&gt;In PyYAML before 5.1, the `yaml.load()` API could execute arbitrary code. In other words, `yaml.safe_load` is not used.&lt;/p&gt;
&lt;p&gt;This was intended to be fixed in 4.1, but due to [breaking changes](https://github.com/yaml/pyyaml/issues/192#issuecomment-401491470), 4.1 was yanked and 5.1 [contains](https://github.com/yaml/pyyaml/issues/207#issuecomment-472520007) the patch for CVE-2017-18342.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: PyYAML&lt;/p&gt;
&lt;p&gt;In PyYAML before 5.1, the `yaml.load()` API could execute arbitrary code. In other words, `yaml.safe_load` is not used.&lt;/p&gt;
&lt;p&gt;This was intended to be fixed in 4.1, but due to [breaking changes](https://github.com/yaml/pyyaml/issues/192#issuecomment-401491470), 4.1 was yanked and 5.1 [contains](https://github.com/yaml/pyyaml/issues/207#issuecomment-472520007) the patch for CVE-2017-18342.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-rprw-h62v-c2w7</guid>
    </item>
    <item>
      <title>PYSEC-2018-49</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2018-49</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyyaml&lt;/p&gt;
&lt;p&gt;In PyYAML before 5.1, the yaml.load() API could execute arbitrary code if used with untrusted data. The load() function has been deprecated in version 5.1 and the &amp;#39;UnsafeLoader&amp;#39; has been introduced for backward compatibility with the function.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyyaml&lt;/p&gt;
&lt;p&gt;In PyYAML before 5.1, the yaml.load() API could execute arbitrary code if used with untrusted data. The load() function has been deprecated in version 5.1 and the &amp;#39;UnsafeLoader&amp;#39; has been introduced for backward compatibility with the function.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2018-49</guid>
    </item>
  </channel>
</rss>
