Bug 2575550 (CVE-2026-129512)

Summary: CVE-2026-129512 log4net: log4net: Log event suppression via improper null byte handling in AdoNetAppender
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedKeywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Apache log4net. Text parameters processed by the database logging appender (AdoNetAppender) are not properly sanitized, allowing null byte characters or invalid Unicode sequences to reach the backend database unchanged. A remote attacker whose input is logged can exploit this issue to trigger database insertion errors, resulting in discarded log entries. Consequently, this flaw allows an attacker to suppress critical security events and evade detection.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2577151, 2577152    
Bug Blocks:    

Description OSIDB Bzimport 2026-11-17 22:22:04 UTC
Improper Neutralization of Null Byte or NUL Character vulnerability in the AdoNetAppender of Apache log4net.

Text parameters were bound unchanged, so a NUL character or an unpaired UTF-16 surrogate reached the database as it was. A database that refuses such a value, such as PostgreSQL, rejected the insert and the event was lost; only the first such loss per appender was reported. A party whose data reaches a log message could suppress that event.

This issue affects Apache log4net: from 1.2.9 before 3.6.0.

Users are recommended to upgrade to version 3.6.0, which fixes the issue.