Log4net vulnerabilitiesRanked by how likely they are to be used.
Log4net is made by Apache. We track 2 published vulnerabilities in it, across 9 versions. None of them is on the list of flaws known to be exploited today. If you run Log4net, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Log4net vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Log4net's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Log4net flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 18%CVE-2018-1285Critical
Apache log4net versions before 2.0.10 do not disable XML external entities when parsing log4net configuration files.
- 6.4%CVE-2006-0743Medium
Format string vulnerability in LocalSyslogAppender in Apache log4net 1.2.9 might allow remote attackers to cause a denial of service (memory corruption and termination) via unknown vectors.
- 0.8%CVE-2026-105241Medium
Improper Handling of Unicode Encoding vulnerability in the SmtpPickupDirAppender of Apache log4net.
- 0.8%CVE-2026-105242Medium
Improper Handling of Exceptional Conditions vulnerability in the aspnet-request pattern converter of Apache log4net.
- 0.8%CVE-2026-105244Medium
Improper Encoding or Escaping of Output vulnerability in the RemoteSyslogAppender of Apache log4net.
- 0.8%CVE-2026-105239Medium
Improper Neutralization of Null Byte or NUL Character vulnerability in the EventLogAppender of Apache log4net.
- 0.8%CVE-2026-105243Medium
Insufficient Logging vulnerability in the EventLogAppender of Apache log4net.
- 0.8%CVE-2026-105240Medium
Improper Neutralization of Null Byte or NUL Character vulnerability in the OutputDebugStringAppender of Apache log4net.
Running Log4net? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Apache log4net versions before 2.0.10 do not disable XML external entities when parsing log4net configuration files. This allows for XXE-based attacks in applications that accept attacker-controlled log4net configuration files.
- Matched to
- Log4net on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 2 published vulnerabilities listed under the name Log4net, across 9 versions.
None of Log4net's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Log4net. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.