log4net vulnerabilities

log4net is a tool to help the programmer output log statements to a variety of output targets. In case of problems with an application, it is helpful to enable logging so that the problem can be located. With log4net it is possible to enable logging at runtime without modifying the application binary. The log4net package is designed so that log statements can remain in shipped code without incurring a high performance cost. It follows that the speed of logging (or rather not logging) is crucial. At the same time, log output can be so voluminous that it quickly becomes overwhelming. One of the distinctive features of log4net is the notion of hierarchical loggers. Using these loggers it is possible to selectively control which log statements are output at arbitrary granularity. log4net is designed with two distinct goals in mind: speed and flexibility

Registry
NuGet
Latest
3.6.0
License
Apache-2.0

3 known advisories

The latest version, 3.6.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:dotnet add package log4net --version 3.6.0

Is your project on an affected log4net?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for log4net

  • MediumCVE-2026-40021GHSA-4f7c-pmjv-c25w10 Apr 2026

    Apache Log4net: Silent log event loss in XmlLayout and XmlLayoutSchemaLog4J due to unescaped XML 1.0 forbidden characters

    Affected
    <3.3.0
    Fixed in
    3.3.0
  • MediumCVE-2006-0743GHSA-f9fr-w54q-772h1 May 2022

    Apache log4net format string vulnerability causes DoS

    Affected
    <1.2.10
    Fixed in
    1.2.10
  • CriticalCVE-2018-1285GHSA-2cwj-8chv-9pp929 Jan 2021

    XML External Entity attack in log4net

    Affected
    <2.0.10
    Fixed in
    2.0.10

Is your log4net version vulnerable?

Which of your client projects still run an old log4net?

NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other NuGet packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.