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


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-jqh7-qm7m-vcgg

## 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 (Improper Output Neutralization for Logs)

## Which versions are affected by CVE-2026-129511?

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


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `log4net` | NuGet | `pkg:nuget/log4net` | From 1.2.9 | 3.6.0 |
| `log4net.Ext.Mail` | NuGet | `pkg:nuget/log4net.Ext.Mail` | From 3.4.0 | 3.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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129511 and fix it if it is affected.

What it is: CVE-2026-129511 is a medium-severity vulnerability in Apache log4net, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129511 in the wild and no public exploit code.

Affected packages and fixed versions:
- log4net (NuGet): affected from 1.2.9; fixed in 3.6.0
- log4net.Ext.Mail (NuGet): affected from 3.4.0; fixed in 3.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129511/ (Markdown: https://insights.sbomify.com/CVE-2026-129511/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129511
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129511
- OSV: https://osv.dev/vulnerability/CVE-2026-129511

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129511/
Summaries are generated and may contain mistakes; the official description above is the record.
