CVE-2026-105243: Apache log4net · Insufficient Logging
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, 28fbfb25678c48a8cc5bc9b94ead0dddfc39ffed
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 28fbfb25678c48a8cc5bc9b94ead0dddfc39ffed.
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 by the vendor advisory recommending upgrade to 3.5.0.
Description
Insufficient Logging vulnerability in the EventLogAppender of Apache log4net. Long messages were truncated to a fixed size that exceeds what the Windows Event Log accepts once the log and source names are counted, and the event log then stored nothing and reported nothing. A party whose data reaches a log message could suppress the whole record by making it long enough. Only applications on Windows that use EventLogAppender are affected. This issue affects Apache log4net: from 1.2.9 before 3.5.0. Users are recommended to upgrade to version 3.5.0, which fixes the issue.
References
- github.com/apache/logging-log4net/pull/315 (opens in a new tab)
- github.com/apache/logging-log4net/commit/28fbfb25678c48a8cc5bc9b94ead0dddfc39ffed (opens in a new tab)
- lists.apache.org/thread.html/jr6fj5skv1vnjbc9jmt8bp151p8ow1rp (opens in a new tab)
- openwall.com/lists/oss-security/2026/10/07/17 (opens in a new tab)