CVE-2026-129511

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

Published Nov 17, 2026 CVSS 3.1 · 5.3 Medium EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

This vulnerability arises in log4net’s FileAppender, RollingFileAppender, UdpAppender and SmtpAppender when a character encoding that uses best‑fit fallback is applied after the XML layout has escaped user data. Fullwidth characters such as U+FF1C, U+FF1E and U+FF02 are silently converted into <, > and ", allowing an attacker to inject crafted XML fragments that become part of the log file. The result is forged log events, for example fake audit entries, which can mislead analysis and compromise log integrity. The weakness is an instance of Improper Output Neutralization for Logs (CWE‑117). No arbitrary code execution or direct access is gained; the flaw affects only the log content.

Affected Systems

Apache Software Foundation’s log4net library, versions beginning with 1.2.9 and continuing through all releases prior to 3.6.0, is vulnerable. On the .NET Framework, the default ANSI single‑byte code page renders the flaw without additional configuration, while on .NET Core / .NET 5+ a single‑byte encoding such as ISO‑8859‑1 must be configured for the issue to manifest.

Risk and Exploitability

The CVSS score of 5.3 classifies the flaw as moderate; the EPSS score is not available, and the vulnerability is not listed in CISA KEV. Exploitation requires the attacker to supply input that is logged, which can arise in a variety of contexts such as web applications, services, or any component that writes to a log4net FileAppender or related appenders. The attack scale is limited to the integrity of log data; however, forged logs can be used to mislead investigations or cover malicious activity. The best‑fit conversion is performed automatically by the encoding system, so no special steps are needed beyond having the vulnerable configuration.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade log4net to version 3.6.0 or later, which removes the best‑fit encoding path in all affected appenders.
  • If an upgrade cannot be performed immediately, set the appender’s encoding to a multi‑byte encoding such as UTF‑8 or explicitly disable the use of single‑byte encodings to prevent best‑fit fallbacks.
  • If the affected appenders are not essential, remove or disable FileAppender, RollingFileAppender, UdpAppender, and SmtpAppender from the logging configuration, or switch to a non‑XML layout for the generated log files.

Generated by OpenCVE AI on November 18, 2026 at 03:03 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
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.
Title Apache log4net: Best-fit encoding in FileAppender lets fullwidth text forge XML log events
Weaknesses CWE-117
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Subscriptions

No data.

Weaknesses
  • CWE-117

    Improper Output Neutralization for Logs

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 18, 2026, 2:06 AM
Reserved
Nov 15, 2026, 8:28 PM
Status
Received
Published
Nov 17, 2026, 11:17 PM
Modified
Nov 18, 2026, 2:17 AM