Skip to content
VulniPulse
Medium5.3Apache Software Foundation Updated

CVE-2026-129510: Improper Output Neutralization for Logs vulnerability in the XmlLayout and XmlLayoutSchemaLog4J of Apache log4net

This Apache advisory covers CVE-2026-129510. Related products: Apache log4net.

Open the Apache advisory

Key facts

Vendor rating
Medium, CVSS 5.3
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N · base score 5.3, scored by apacheAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: low. Availability impact: none.
Weakness
  • CWE-117 Improper Output Neutralization for Logs
EPSS
0.41% chance of exploitation in the next 30 days (36th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Versions named
1.2.9 before 3.6.0
Fixed in
3.6.0
Source published
Source revised
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Related products & platforms

Apache Software FoundationLog4j

Description

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.

Text from the source record.

Versions named by the source
  • 1.2.9 before 3.6.0

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-129510

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

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

Apache Software Foundation advisories, November 2026All Apache Software Foundation advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache