Improper Encoding or Escaping of Output Affecting log4net package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.12% (31st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Encoding or Escaping of Output vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIAN11-LOG4NET-16032309
  • published14 Apr 2026
  • disclosed10 Apr 2026

Introduced: 10 Apr 2026

NewCVE-2026-40021  (opens in a new tab)
CWE-116  (opens in a new tab)

How to fix?

There is no fixed version for Debian:11 log4net.

NVD Description

Note: Versions mentioned in the description apply only to the upstream log4net package and not the log4net package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

Apache Log4net's XmlLayout https://logging.apache.org/log4net/manual/configuration/layouts.html#layout-list and XmlLayoutSchemaLog4J https://logging.apache.org/log4net/manual/configuration/layouts.html#layout-list , in versions before 3.3.0, fail to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets in MDC property keys and values, as well as the identity field that may carry attacker-influenced data. This causes an exception during serialization and the silent loss of the affected log event.

An attacker who can influence any of these fields can exploit this to suppress individual log records, impairing audit trails and detection of malicious activity.

Users are advised to upgrade to Apache Log4net 3.3.0, which fixes this issue.