CVE
Apache log4net: Best-fit encoding in FileAppender lets fullwidth text forge XML log events
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 3.6.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.6.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 32/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach10/20Affects NuGet packages
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.6.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129511 (Apache log4net: Best-fit encoding in FileAppender lets fullwidth text forge XML log events), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129511 (entry last updated 2026-11-18):
Affected:
- NuGet package log4net: from 1.2.9, fixed in 3.6.0
- NuGet package log4net.Ext.Mail: from 3.4.0, fixed in 3.6.0
- NuGet package log4net: version range not reported
Fixed versions: 3.6.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129511 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129511 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (NuGet): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/v2oljwjcboxk0tvyy5v86o2fjlslx1zt
- https://github.com/apache/logging-log4net/pull/355
- https://github.com/apache/logging-log4net/commit/735db80ab163ef08c54d2cc4d3d576b22b77f4bc
- http://www.openwall.com/lists/oss-security/2026/11/17/35
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129511
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129511"}.Timeline
- CVE published1 day
- First seen by cve.now
- Record last updated
Affected versions
- log4netNuGet
From 1.2.9 · fixed in 3.6.0
Fixed in 3.6.0 (released Nov 12, 2026, 5 days before disclosure).
- log4net.Ext.MailNuGet
From 3.4.0 · fixed in 3.6.0
- log4netNuGet
Version range not reported
The latest release, 3.6.0, is not affected.
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Write-ups · 1
Establishes: Technical detail and context.
- Link
Other links · 2
- Patch
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129511
Is CVE-2026-129511 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-129511?
log4net (NuGet): from 1.2.9 before 3.6.0. log4net.Ext.Mail (NuGet): from 3.4.0 before 3.6.0.Source: cve.now feed data
How do I fix CVE-2026-129511?
Upgrade to a fixed version: 3.6.0.Source: cve.now feed data