<?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>Fri, 02 Oct 2026 17:33:01 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-57076</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-57076</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: perl-yaml-syck, Alpaquita:25: perl-yaml-syck, Alpaquita:stream: perl-yaml-syck&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: perl-yaml-syck, Alpaquita:25: perl-yaml-syck, Alpaquita:stream: perl-yaml-syck&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-57076</guid>
    </item>
    <item>
      <title>fkie_cve-2026-57076</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-57076</link>
      <description>&lt;p&gt;YAML::Syck versions before 1.47 for Perl allow a heap use-after-free via an anchor name reused as an anchors-table key in syck_hdlr_add_anchor.&lt;/p&gt;
&lt;p&gt;In the bundled libsyck an anchor name allocated by syck_strndup is stored both as node-&amp;gt;anchor, freed when the node is freed, and as the key in the parser&amp;#39;s anchors table. Freeing the node frees the shared key, and a later anchor redefinition makes st_delete compare against the freed key, so st_strcmp reads freed heap memory. Anchors are a standard YAML feature and need no special flags, so this is reached on the default Load path.&lt;/p&gt;
&lt;p&gt;Any caller that runs Load or LoadFile on an untrusted document that redefines an anchor reaches the read of freed memory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;YAML::Syck versions before 1.47 for Perl allow a heap use-after-free via an anchor name reused as an anchors-table key in syck_hdlr_add_anchor.&lt;/p&gt;
&lt;p&gt;In the bundled libsyck an anchor name allocated by syck_strndup is stored both as node-&amp;gt;anchor, freed when the node is freed, and as the key in the parser&amp;#39;s anchors table. Freeing the node frees the shared key, and a later anchor redefinition makes st_delete compare against the freed key, so st_strcmp reads freed heap memory. Anchors are a standard YAML feature and need no special flags, so this is reached on the default Load path.&lt;/p&gt;
&lt;p&gt;Any caller that runs Load or LoadFile on an untrusted document that redefines an anchor reaches the read of freed memory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-57076</guid>
    </item>
    <item>
      <title>GHSA-q6x2-vfpr-9j7p</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-q6x2-vfpr-9j7p</link>
      <description>&lt;p&gt;YAML::Syck versions before 1.47 for Perl allow a heap use-after-free via an anchor name reused as an anchors-table key in syck_hdlr_add_anchor.&lt;/p&gt;
&lt;p&gt;In the bundled libsyck an anchor name allocated by syck_strndup is stored both as node-&amp;gt;anchor, freed when the node is freed, and as the key in the parser&amp;#39;s anchors table. Freeing the node frees the shared key, and a later anchor redefinition makes st_delete compare against the freed key, so st_strcmp reads freed heap memory. Anchors are a standard YAML feature and need no special flags, so this is reached on the default Load path.&lt;/p&gt;
&lt;p&gt;Any caller that runs Load or LoadFile on an untrusted document that redefines an anchor reaches the read of freed memory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;YAML::Syck versions before 1.47 for Perl allow a heap use-after-free via an anchor name reused as an anchors-table key in syck_hdlr_add_anchor.&lt;/p&gt;
&lt;p&gt;In the bundled libsyck an anchor name allocated by syck_strndup is stored both as node-&amp;gt;anchor, freed when the node is freed, and as the key in the parser&amp;#39;s anchors table. Freeing the node frees the shared key, and a later anchor redefinition makes st_delete compare against the freed key, so st_strcmp reads freed heap memory. Anchors are a standard YAML feature and need no special flags, so this is reached on the default Load path.&lt;/p&gt;
&lt;p&gt;Any caller that runs Load or LoadFile on an untrusted document that redefines an anchor reaches the read of freed memory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-q6x2-vfpr-9j7p</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11299-1 — perl-YAML-Syck-1.470.0-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11299-1</link>
      <description>&lt;p&gt;perl-YAML-Syck-1.470.0-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;perl-YAML-Syck-1.470.0-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11299-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-57076</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-57076</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: libyaml-syck-perl, Ubuntu:Pro:18.04:LTS: libyaml-syck-perl, Ubuntu:Pro:20.04:LTS: libyaml-syck-perl, Ubuntu:Pro:22.04:LTS: libyaml-syck-perl, Ubuntu:Pro:24.04:LTS: libyaml-syck-perl, Ubuntu:26.04:LTS: libyaml-syck-perl&lt;/p&gt;
&lt;p&gt;YAML::Syck versions before 1.47 for Perl allow a heap use-after-free via an anchor name reused as an anchors-table key in syck_hdlr_add_anchor. In the bundled libsyck an anchor name allocated by syck_strndup is stored both as node-&amp;gt;anchor, freed when the node is freed, and as the key in the parser&amp;#39;s anchors table. Freeing the node frees the shared key, and a later anchor redefinition makes st_delete compare against the freed key, so st_strcmp reads freed heap memory. Anchors are a standard YAML feature and need no special flags, so this is reached on the default Load path. Any caller that runs Load or LoadFile on an untrusted document that redefines an anchor reaches the read of freed memory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: libyaml-syck-perl, Ubuntu:Pro:18.04:LTS: libyaml-syck-perl, Ubuntu:Pro:20.04:LTS: libyaml-syck-perl, Ubuntu:Pro:22.04:LTS: libyaml-syck-perl, Ubuntu:Pro:24.04:LTS: libyaml-syck-perl, Ubuntu:26.04:LTS: libyaml-syck-perl&lt;/p&gt;
&lt;p&gt;YAML::Syck versions before 1.47 for Perl allow a heap use-after-free via an anchor name reused as an anchors-table key in syck_hdlr_add_anchor. In the bundled libsyck an anchor name allocated by syck_strndup is stored both as node-&amp;gt;anchor, freed when the node is freed, and as the key in the parser&amp;#39;s anchors table. Freeing the node frees the shared key, and a later anchor redefinition makes st_delete compare against the freed key, so st_strcmp reads freed heap memory. Anchors are a standard YAML feature and need no special flags, so this is reached on the default Load path. Any caller that runs Load or LoadFile on an untrusted document that redefines an anchor reaches the read of freed memory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-57076</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2508 — cPanel cPanel/WHM: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2508</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in cPanel cPanel/WHM ausnutzen, um möglicherweise beliebigen Code auszuführen, vertrauliche Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder einen Denial-of-Service-Zustand herbeizuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in cPanel cPanel/WHM ausnutzen, um möglicherweise beliebigen Code auszuführen, vertrauliche Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder einen Denial-of-Service-Zustand herbeizuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2508</guid>
    </item>
  </channel>
</rss>
