CVE-2026-105240: 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 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.5.0, 6046fe9d7f353b49fe995361c071ec2eea8f7ef6
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 6046fe9d7f353b49fe995361c071ec2eea8f7ef6.
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.
Description
CVE-2026-105240 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 OutputDebugStringAppender on Windows platforms. When a null byte appears in logged content, it prematurely terminates the debug output record, causing loss of subsequent log data including exception details. This allows an attacker who can influence log messages to hide parts of the 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/6046fe9d7f353b49fe995361c071ec2eea8f7ef6 (opens in a new tab)
- lists.apache.org/thread.html/gyw2d4ppy82t1vlpdknkfd1nmzp21z17 (opens in a new tab)
- openwall.com/lists/oss-security/2026/10/07/18 (opens in a new tab)