CVE-2026-105239: Apache log4net · Improper Neutralization of Null Byte or NUL Character
Affects Apache log4netSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.5.0 when convenient.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.5.0, dc5855a0720c91590fd7a81d729ea01fdd69e000
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 6 Oct 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 20 Nov 2026.
What to do
Upgrade Apache log4net and log4net to 3.5.0; Apache log4net to dc5855a0720c91590fd7a81d729ea01fdd69e000.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache log4net | Affected
| Fixed in
|
| Apache Software FoundationApache log4net | Affected
| Fixed in
|
NuGetlog4netpkg:nuget/log4netOther 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.5.0 or later, where this issue is fixed. No other mitigations are indicated. Since this is a software vulnerability, patching is the recommended and effective remediation.
Description
CVE-2026-105239 is a medium severity vulnerability in Apache log4net affecting versions from 1.2.9 up to but not including 3.5.0. It involves improper neutralization of null byte characters in the EventLogAppender on Windows. A null byte in logged content prematurely ends the Windows Event Log record, causing subsequent data such as exception text and trailing fields to be omitted silently. This allows data that reaches the log message to hide the rest of that log record. The issue is fixed in version 3.5.0.
References
- github.com/apache/logging-log4net/pull/315 (opens in a new tab)
- github.com/apache/logging-log4net/commit/dc5855a0720c91590fd7a81d729ea01fdd69e000 (opens in a new tab)
- lists.apache.org/thread.html/9fx1qo5hc0tg8ym0t6p9gt1zpb2qlxpq (opens in a new tab)
- openwall.com/lists/oss-security/2026/10/07/14 (opens in a new tab)