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.
Show the promptExplain CVE-2026-129510 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-129510?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-129510?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-129510 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
apache software foundation:apache log4net
Versions
From the CNA's record in the CVE List.
Product
Affected
Apache Software Foundation Apache log4net
from 1.2.9 before 3.6.0
Attack patterns (CAPEC)
CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
CAPEC-93 Log Injection-Tampering-Forging Likelihood: High · Severity: High