<?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>Fri, 09 Oct 2026 15:29:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-40023 — Apache Log4cxx, Apache Log4cxx (Conan), Apache Log4cxx (Brew): Silent log event loss in XMLLayout due to unescaped XML…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-40023</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Log4cxx, Apache Software Foundation Apache Log4cxx (Conan), Apache Software Foundation Apache Log4cxx (Brew)&lt;/p&gt;
&lt;p&gt;Apache Log4cxx&amp;#39;s  XMLLayout https://logging.apache.org/log4cxx/1.7.0/classlog4cxx_1_1xml_1_1XMLLayout.html , in versions before 1.7.0, fails to sanitize characters forbidden by the  XML 1.0 specification https://www.w3.org/TR/xml/#charsets  in log messages, NDC, and MDC property keys and values, producing invalid XML output. Conforming XML parsers must reject such documents with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.&lt;/p&gt;
&lt;p&gt;An attacker who can influence logged data can exploit this to suppress individual log records, impairing audit trails and detection of malicious activity.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to Apache Log4cxx 1.7.0, which fixes this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Log4cxx, Apache Software Foundation Apache Log4cxx (Conan), Apache Software Foundation Apache Log4cxx (Brew)&lt;/p&gt;
&lt;p&gt;Apache Log4cxx&amp;#39;s  XMLLayout https://logging.apache.org/log4cxx/1.7.0/classlog4cxx_1_1xml_1_1XMLLayout.html , in versions before 1.7.0, fails to sanitize characters forbidden by the  XML 1.0 specification https://www.w3.org/TR/xml/#charsets  in log messages, NDC, and MDC property keys and values, producing invalid XML output. Conforming XML parsers must reject such documents with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.&lt;/p&gt;
&lt;p&gt;An attacker who can influence logged data can exploit this to suppress individual log records, impairing audit trails and detection of malicious activity.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to Apache Log4cxx 1.7.0, which fixes this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-40023</guid>
    </item>
  </channel>
</rss>
