CVE-2026-105240
Improper Neutralization of Null Byte or NUL Character vulnerability …
Improper Neutralization of Null Byte or NUL Character vulnerability in the OutputDebugStringAppender of Apache log4net. A NUL character in logged content ended the debug output record at that point, so everything the layout rendered after it, including exception text and trailing fields, was silently lost. A party whose data reaches a log message could hide the rest of that record. Only applications on Windows that use OutputDebugStringAppender 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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/apache/logging-log4net/commit/6046fe9d7f353b49fe995361c071ec2eea8f7ef6
- github.com/apache/logging-log4net/pull/315
- lists.apache.org/thread.html/gyw2d4ppy82t1vlpdknkfd1nmzp21z17
- www.openwall.com/lists/oss-security/2026/10/07/18
- nvd.nist.gov/vuln/detail/CVE-2026-105240
- cve.org/CVERecord?id=CVE-2026-105240
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.