<?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>Wed, 18 Nov 2026 20:14:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-129511 — Apache log4net: Best-fit encoding in FileAppender lets fullwidth text forge XML log events</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-129511</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache log4net&lt;/p&gt;
&lt;p&gt;Improper Output Neutralization for Logs vulnerability in the FileAppender, RollingFileAppender, UdpAppender and SmtpAppender of Apache log4net.&lt;/p&gt;
&lt;p&gt;Characters the configured encoding could not represent were converted by that encoding&amp;#39;s best-fit fallback, which turns fullwidth characters such as U+FF1C, U+FF1E and U+FF02 into &amp;lt;, &amp;gt; and &amp;#34;. The conversion happened after XmlLayout or XmlLayoutSchemaLog4J had escaped the text, so a party whose data reaches a log message could forge complete log events in an XML log, for example a fake audit entry. On .NET Framework this needs no configuration where the ANSI code page is single-byte, since that is the default encoding; on .NET it needs a configured single-byte encoding such as ISO-8859-1. This is the best-fit conversion described by the WorstFit research.&lt;/p&gt;
&lt;p&gt;This issue affects Apache log4net: from 1.2.9 before 3.6.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 3.6.0, which fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache log4net&lt;/p&gt;
&lt;p&gt;Improper Output Neutralization for Logs vulnerability in the FileAppender, RollingFileAppender, UdpAppender and SmtpAppender of Apache log4net.&lt;/p&gt;
&lt;p&gt;Characters the configured encoding could not represent were converted by that encoding&amp;#39;s best-fit fallback, which turns fullwidth characters such as U+FF1C, U+FF1E and U+FF02 into &amp;lt;, &amp;gt; and &amp;#34;. The conversion happened after XmlLayout or XmlLayoutSchemaLog4J had escaped the text, so a party whose data reaches a log message could forge complete log events in an XML log, for example a fake audit entry. On .NET Framework this needs no configuration where the ANSI code page is single-byte, since that is the default encoding; on .NET it needs a configured single-byte encoding such as ISO-8859-1. This is the best-fit conversion described by the WorstFit research.&lt;/p&gt;
&lt;p&gt;This issue affects Apache log4net: from 1.2.9 before 3.6.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 3.6.0, which fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-129511</guid>
    </item>
  </channel>
</rss>
