https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2026-105244.htmlhttps://patchthecve.com/cve/CVE-2026-105244.htmlFri, 09 Oct 2026 15:18:44 +0000MEDIUM 5.3: Improper Encoding or Escaping of Output vulnerability in the RemoteSyslogAppender of Apache log4net. Every character outside visible ASCII and space was removed from the record instead of being escaped, so non-ASCII text and control characters such as tabs disappeared without notice. A party whose https://patchthecve.com/cve/CVE-2026-105243.htmlhttps://patchthecve.com/cve/CVE-2026-105243.htmlFri, 09 Oct 2026 15:26:03 +0000MEDIUM 5.3: Insufficient Logging vulnerability in the EventLogAppender of Apache log4net. Long messages were truncated to a fixed size that exceeds what the Windows Event Log accepts once the log and source names are counted, and the event log then stored nothing and reported nothing. A party whose data reachehttps://patchthecve.com/cve/CVE-2026-105242.htmlhttps://patchthecve.com/cve/CVE-2026-105242.htmlFri, 09 Oct 2026 15:28:34 +0000MEDIUM 5.3: Improper Handling of Exceptional Conditions vulnerability in the aspnet-request pattern converter of Apache log4net. Reading request parameters triggers ASP.NET request validation, so a request carrying content such as markup made the layout throw and the appender discarded the whole event. A sendehttps://patchthecve.com/cve/CVE-2026-105241.htmlhttps://patchthecve.com/cve/CVE-2026-105241.htmlFri, 09 Oct 2026 15:29:42 +0000MEDIUM 5.3: Improper Handling of Unicode Encoding vulnerability in the SmtpPickupDirAppender of Apache log4net. Content that the mail file writer cannot encode, such as an unpaired UTF-16 surrogate, made the write throw. Every buffered event in the batch was discarded, not only the one carrying the content, anhttps://patchthecve.com/cve/CVE-2026-105240.htmlhttps://patchthecve.com/cve/CVE-2026-105240.htmlFri, 09 Oct 2026 15:41:47 +0000MEDIUM 5.3: 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 silenthttps://patchthecve.com/cve/CVE-2026-105239.htmlhttps://patchthecve.com/cve/CVE-2026-105239.htmlFri, 09 Oct 2026 15:44:02 +0000MEDIUM 5.3: Improper Neutralization of Null Byte or NUL Character vulnerability in the EventLogAppender of Apache log4net. A NUL character in logged content ended the Windows Event Log record at that point, so everything the layout rendered after it, including exception text and trailing fields, was silently nhttps://patchthecve.com/cve/CVE-2026-40021.htmlhttps://patchthecve.com/cve/CVE-2026-40021.htmlMon, 26 Oct 2026 21:10:00 +0000MEDIUM 5.3: 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 s