# CVE-2026-129510: Apache log4net: Culture-sensitive CDATA end search in XmlLayout hides later log events


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-834f-w75c-wxm6

## What is CVE-2026-129510?

CVE-2026-129510 is a medium-severity vulnerability in Apache log4net, published on 17 Nov 2026. 

### Official 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.

Weakness: CWE-117 (Improper Output Neutralization for Logs)

## Which versions are affected by CVE-2026-129510?

1 open source package ship an affected version, including log4net.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `log4net` | NuGet | `pkg:nuget/log4net` | From 1.2.9 | 3.6.0 |

## How do I fix CVE-2026-129510?

Upgrade log4net to 3.6.0 or later.

## Is CVE-2026-129510 being exploited?

There is no known exploitation of CVE-2026-129510 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129510 and fix it if it is affected.

What it is: CVE-2026-129510 is a medium-severity vulnerability in Apache log4net, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129510 in the wild and no public exploit code.

Affected packages and fixed versions:
- log4net (NuGet): affected from 1.2.9; fixed in 3.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129510/ (Markdown: https://insights.sbomify.com/CVE-2026-129510/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129510
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129510
- OSV: https://osv.dev/vulnerability/CVE-2026-129510

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129510/
Summaries are generated and may contain mistakes; the official description above is the record.
