Skip to main content
Menu
CVEs

CVE

Apache log4net log event hiding in XmlLayout via CDATA parsing

CVE-2026-129510EUVD-2026-128191GHSA-834F-W75C-WXM6

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.6.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.6.0.

Published
Last modified
Reference
Last checked
32/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Apache log4net's XmlLayout and XmlLayoutSchemaLog4J mishandle the end marker of CDATA sections in log messages. A remote attacker who can get data into a log message, without logging in, can hide later log events from a program that parses the XML log.

Written by a model from the sources below. Verify against them.

Original 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.

cve.now Index

32Pcve.now Index 32 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Affects NuGet packages
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.6.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129510 (Apache log4net: Culture-sensitive CDATA end search in XmlLayout hides later log events), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129510 (entry last updated 2026-11-18):
Affected:
- NuGet package log4net: from 1.2.9, fixed in 3.6.0
- NuGet package log4net: version range not reported
Fixed versions: 3.6.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129510 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129510 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (NuGet): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/wdwlygr9v6wv24gh3w364syttqzkv88m
- https://github.com/apache/logging-log4net/pull/355
- https://github.com/apache/logging-log4net/commit/80d955e8c8f1e9f094c2b3d1c142147ee8b8b805
- http://www.openwall.com/lists/oss-security/2026/11/17/34
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129510
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129510"}.

Timeline

  1. CVE published1 day
  2. First seen by cve.now
  3. Record last updated

Affected versions

  • log4netNuGet

    From 1.2.9 · fixed in 3.6.0

    Fixed in 3.6.0 (released Nov 12, 2026, 5 days before disclosure).

  • log4netNuGet

    Version range not reported

    The latest release, 3.6.0, is not affected.

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 1

Establishes: Technical detail and context.

  1. Link

Other links · 2

  1. Patch
  2. Patch

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129510

Is CVE-2026-129510 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129510?

log4net (NuGet): from 1.2.9 before 3.6.0.Source: cve.now feed data

How do I fix CVE-2026-129510?

Upgrade to a fixed version: 3.6.0.Source: cve.now feed data

More CVEs