Skip to content
Fencer Intel
medium 5.3

CVE-2026-129511 json

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

published 5h ago modified 1h ago also EUVD-2026-128194

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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.

Patch / fix

  • Apache Software Foundation Apache log4net 3.6.0

Is CVE-2026-129511 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected products

  • Apache Software Foundation Apache log4net

Classification

Weakness
  • CWE-117 Improper Output Neutralization for Logs

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.