Answer in brief
CVE-2026-129511 records a Medium severity (CVSS 5.3) vulnerability in Apache log4net: Best-fit encoding in FileAppender lets fullwidth text forge XML log events. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/log4net (generic), Apache Software Foundation/log4net (generic), Apache Software Foundation/log4net.Ext.Mail (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/log4net (generic), Apache Software Foundation/log4net (generic), Apache Software Foundation/log4net.Ext.Mail (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/log4netgeneric | >=1.2.9 <3.6.0 | 3.6.0 |
| Apache Software Foundation/log4netgeneric | >=02e1e115435888485f2e28b414d267e39e799e07 <735db80ab163ef08c54d2cc4d3d576b22b77f4bc | 735db80ab163ef08c54d2cc4d3d576b22b77f4bc |
| Apache Software Foundation/log4net.Ext.Mailgeneric | >=3.4.0 <3.6.0 | 3.6.0 |
Published upstream
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.