Intel

AIKIDO-2026-373947

log4net is vulnerable to Improper Handling of Unicode Encoding

CVE-2026-105241Published Oct 30, 2026
October 30, 2026

53

CVE Score

Medium

Improper Handling of Unicode Encoding

Are you affected? Scan for Free

TL;DR

Before the fix, SmtpPickupDirAppender wrote its pickup-directory mail with File.CreateText, whose UTF-8 encoder throws on characters it cannot encode, such as an unpaired UTF-16 surrogate in a logged message. One such event, supplied by any party whose data reaches a log message, aborted the whole batch write: the remaining buffered events were never written and a truncated mail was left for the pickup service to send. Only applications that configure SmtpPickupDirAppender are exposed. The fix writes with a non-throwing UTF-8 encoder and escapes unpaired surrogates, so one unencodable event no longer discards the batch.

How do I fix this?

Upgrade the log4net package to 3.5.0 or later.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and use a SmtpPickupDirAppender whose logged messages include content from other parties, such as user-supplied request data.

Package

Versions

1.2.10 - 3.4.0

Fixed in 3.5.0

Background info

log4net is vulnerable to Improper Handling of Unicode Encoding in versions 1.2.10 - 3.4.0.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea