<?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>Tue, 29 Sep 2026 18:58:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-8732 — libxml2 xmlcatalog xmlParseSGMLCatalog recursion</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-8732</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; libxml2, Siemens RUGGEDCOM RST2428P&lt;/p&gt;
&lt;p&gt;A vulnerability was found in libxml2 up to 2.14.5. It has been declared as problematic. This vulnerability affects the function xmlParseSGMLCatalog of the component xmlcatalog. The manipulation leads to uncontrolled recursion. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The code maintainer explains, that &amp;#34;[t]he issue can only be triggered with untrusted SGML catalogs and it makes absolutely no sense to use untrusted catalogs. I also doubt that anyone is still using SGML catalogs at all.&amp;#34;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; libxml2, Siemens RUGGEDCOM RST2428P&lt;/p&gt;
&lt;p&gt;A vulnerability was found in libxml2 up to 2.14.5. It has been declared as problematic. This vulnerability affects the function xmlParseSGMLCatalog of the component xmlcatalog. The manipulation leads to uncontrolled recursion. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The code maintainer explains, that &amp;#34;[t]he issue can only be triggered with untrusted SGML catalogs and it makes absolutely no sense to use untrusted catalogs. I also doubt that anyone is still using SGML catalogs at all.&amp;#34;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-8732</guid>
    </item>
    <item>
      <title>USN-7974-1 — libxml2 vulnerabilities</title>
      <link>https://vulnerability.circl.lu/vuln/usn-7974-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: libxml2, Ubuntu:Pro:16.04:LTS: libxml2, Ubuntu:Pro:18.04:LTS: libxml2, Ubuntu:Pro:20.04:LTS: libxml2, Ubuntu:22.04:LTS: libxml2, Ubuntu:24.04:LTS: libxml2, Ubuntu:25.10: libxml2&lt;/p&gt;
&lt;p&gt;It was discovered that libxml2 incorrectly handled maliciously crafted SGML
catalog files. An attacker could possibly use this issue to cause libxml2
to consume excessive resources, leading to a denial of service.
(CVE-2025-8732)&lt;/p&gt;
&lt;p&gt;It was discovered that libxml2 incorrectly handled recursive include
directories with the RelaxNG parser. An attacker could possibly use this
issue to cause libxml2 to consume excessive resources, leading to a denial
of service. (CVE-2026-0989)&lt;/p&gt;
&lt;p&gt;Nick Wellnhofer discovered that libxml2 incorrectly parsed catalogs with
self-referencing URI delegates. An attacker could possibly use this issue
to cause libxml2 to consume excessive resources, leading to a denial of
service. (CVE-2026-0990)&lt;/p&gt;
&lt;p&gt;Nick Wellnhofer discovered that libxml2 inefficiently parsed catalogs
linked with repeating nextCatalog elements. An attacker could possibly use
this issue to cause libxml2 to use excessive resources, leading to a denial
of service. (CVE-2026-0992)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: libxml2, Ubuntu:Pro:16.04:LTS: libxml2, Ubuntu:Pro:18.04:LTS: libxml2, Ubuntu:Pro:20.04:LTS: libxml2, Ubuntu:22.04:LTS: libxml2, Ubuntu:24.04:LTS: libxml2, Ubuntu:25.10: libxml2&lt;/p&gt;
&lt;p&gt;It was discovered that libxml2 incorrectly handled maliciously crafted SGML
catalog files. An attacker could possibly use this issue to cause libxml2
to consume excessive resources, leading to a denial of service.
(CVE-2025-8732)&lt;/p&gt;
&lt;p&gt;It was discovered that libxml2 incorrectly handled recursive include
directories with the RelaxNG parser. An attacker could possibly use this
issue to cause libxml2 to consume excessive resources, leading to a denial
of service. (CVE-2026-0989)&lt;/p&gt;
&lt;p&gt;Nick Wellnhofer discovered that libxml2 incorrectly parsed catalogs with
self-referencing URI delegates. An attacker could possibly use this issue
to cause libxml2 to consume excessive resources, leading to a denial of
service. (CVE-2026-0990)&lt;/p&gt;
&lt;p&gt;Nick Wellnhofer discovered that libxml2 inefficiently parsed catalogs
linked with repeating nextCatalog elements. An attacker could possibly use
this issue to cause libxml2 to use excessive resources, leading to a denial
of service. (CVE-2026-0992)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-7974-1</guid>
    </item>
  </channel>
</rss>
