CVE-2026-129511: Improper Output Neutralization for Logs vulnerability in the FileAppender, RollingFileAppender, UdpAppender and SmtpAppender of Apache log4net
This Apache advisory covers CVE-2026-129511. Related products: Apache log4net.
- CVE-2026-129511
Key facts
- Vendor rating
- Medium, CVSS 5.3
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N· base score 5.3, scored by apacheAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: low. Availability impact: none.- Weakness
- CWE-117 Improper Output Neutralization for Logs
- EPSS
- 0.41% chance of exploitation in the next 30 days (36th percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Versions named
- 1.2.9 before 3.6.0
- Fixed in
- 3.6.0
- Source published
- Source revised
- Listed by VulniPulse
- Record changed
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Related products & platforms
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.
Text from the source record.
- 1.2.9 before 3.6.0
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-129511
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- Users are recommended to upgrade to version 3.6.0, which fixes the issue.
More Apache Software Foundation advisories
CVE-2026-129512Nov 17, 2026Improper Neutralization of Null Byte or NUL Character vulnerability in the AdoNetAppenderCVE-2026-129510Nov 17, 2026Improper Output Neutralization for Logs vulnerability in the XmlLayoutCVE-2026-132129Nov 19, 2026Passing a different column type while using deprecated range predicatesCVE-2026-120404Nov 19, 2026The built-in regular expression name finder for latitude and longitude coordinates usesCVE-2026-132079Nov 18, 2026Insufficient Session Expiration vulnerability in the Apache Iggy Go SDKCVE-2026-118493Nov 18, 2026Insertion of Sensitive Information into Log File vulnerability in the Apache Iggy server
Apache Software Foundation advisories, November 2026All Apache Software Foundation advisories
Get an email when Apache publishes the next one.
See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.