CVE-2026-129511 Apache log4net: Best-fit encoding in FileAppender lets fullwidth text forge XML log events

Medium 5.3 Published Updated
Exploited in the wild
Not known
Fix
None listed

What is CVE-2026-129511?

CVE-2026-129511 is a medium-severity vulnerability in Apache log4net, published on 17 Nov 2026.

Official description

Improper Output Neutralization for Logs vulnerability in the FileAppender, RollingFileAppender, UdpAppender and SmtpAppender of Apache log4net.

Characters the configured encoding could not represent were converted by that encoding's best-fit fallback, which turns fullwidth characters such as U+FF1C, U+FF1E and U+FF02 into <, > and ". 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.

This issue affects Apache log4net: from 1.2.9 before 3.6.0.

Users are recommended to upgrade to version 3.6.0, which fixes the issue.

Weakness: CWE-117

Which versions are affected by CVE-2026-129511?

2 open source packages ship an affected version, including log4net and log4net.Ext.Mail.

PackageAffectedFixed in
log4net NuGet
pkg:nuget/log4net
From 1.2.93.6.0
log4net.Ext.Mail NuGet
pkg:nuget/log4net.Ext.Mail
From 3.4.03.6.0

How do I fix CVE-2026-129511?

Upgrade log4net to 3.6.0 or later.

Is CVE-2026-129511 being exploited?

There is no known exploitation of CVE-2026-129511 in the wild and no public exploit code.

Sources

Also known as GHSA-jqh7-qm7m-vcgg.

Is CVE-2026-129511 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free