CVE-2026-105242: Apache log4net · Improper Handling of Exceptional Conditions
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, 145203420c579a703008b4b723b6a080757f4964
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 145203420c579a703008b4b723b6a080757f4964.
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. Patch status is confirmed as fixed in 3.5.0.
Description
CVE-2026-105242 is a medium severity vulnerability in Apache log4net affecting versions from 1.2.11 up to but not including 3.5.0. It involves improper handling of exceptional conditions in the aspnet-request pattern converter. When request parameters trigger ASP.NET request validation and contain markup, the layout throws an exception causing the appender to discard the entire log event. This allows a sender to suppress logging of their own request. The issue only affects applications running on ASP.NET for .NET Framework that use the %aspnet-request layout pattern. Upgrading to version 3.5.0 resolves the vulnerability.
References
- github.com/apache/logging-log4net/pull/316 (opens in a new tab)
- github.com/apache/logging-log4net/commit/145203420c579a703008b4b723b6a080757f4964 (opens in a new tab)
- lists.apache.org/thread.html/zg6dbqm4ztm7j3c21nfsqj0yxm5yrpdx (opens in a new tab)
- openwall.com/lists/oss-security/2026/10/07/16 (opens in a new tab)