Bug 2575546 (CVE-2026-129510)

Summary: CVE-2026-129510 log4net: log4net: Log event masking via improper CDATA delimiter handling
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 log4net. When generating XML-formatted logs, the application improperly detects delimiters used to close character data (CDATA) sections due to culture-sensitive string comparisons. An attacker who supplies input recorded in logs can provide text containing special Unicode characters around the delimiter, leaving the section unclosed. Consequently, downstream XML log parsers may treat subsequent log entries as part of the attacker's message or fail to parse the log entirely, allowing an attacker to conceal subsequent log events and tamper with audit trails.
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: 2577146, 2577147    
Bug Blocks:    

Description OSIDB Bzimport 2026-11-17 22:21:34 UTC
Improper Output Neutralization for Logs vulnerability in the XmlLayout and XmlLayoutSchemaLog4J of Apache log4net.

Both layouts split a message holding the CDATA end marker into several CDATA sections, but searched for the marker with a culture-sensitive comparison. Ignorable characters or a combining mark around the marker made the search miss it, so the CDATA section stayed open. From 3.3.1 on, an XML parser then reads the following log events as part of that message; earlier versions leave the log file not well-formed. A party whose data reaches a log message could hide later log events from a consumer that parses the XML log.

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.