CVE-2026-129511: Apache log4net · Log Injection
Affects Apache log4netSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.6.0 when convenient.
Data as of 17 Nov 2026, 22:49 UTC
Thin evidence
One scorer or none| CNA (apache) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 3.6.0, 735db80ab163ef08c54d2cc4d3d576b22b77f4bc
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Apache log4net and log4net and log4net.Ext.Mail to 3.6.0; Apache log4net to 735db80ab163ef08c54d2cc4d3d576b22b77f4bc.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache log4netlog4net | Affected
| Fixed in
|
| Apache log4netlog4net.Ext.Mail | Affected
| Fixed in
|
| Apache log4netlog4net | Affected
| Fixed in
|
NuGetlog4netpkg:nuget/log4netOther threats | Affected
| Fixed in
|
NuGetlog4net.Ext.Mailpkg:nuget/log4net.Ext.MailOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade Apache log4net to version 3.6.0 or later, where this vulnerability is fixed. No other mitigations are indicated or required according to the vendor advisory.
Description
CVE-2026-129511 is a vulnerability in Apache log4net versions from 1.2.9 up to but not including 3.6.0. It involves improper output neutralization for logs in several appenders, allowing specially crafted input to forge complete log events in XML logs. The issue arises due to best-fit fallback encoding converting certain fullwidth Unicode characters into ASCII characters after XML escaping, enabling log injection attacks. The vulnerability is fixed in version 3.6.0.