# CVE-2026-129512: Apache log4net: AdoNetAppender loses an event whose text the database cannot store


- **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-qwr2-h49j-j5m8

## What is CVE-2026-129512?

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

### Official description

Improper Neutralization of Null Byte or NUL Character vulnerability in the AdoNetAppender of Apache log4net.

Text parameters were bound unchanged, so a NUL character or an unpaired UTF-16 surrogate reached the database as it was. A database that refuses such a value, such as PostgreSQL, rejected the insert and the event was lost; only the first such loss per appender was reported. A party whose data reaches a log message could suppress that event.

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-158 (Improper Neutralization of Null Byte or NUL Character)

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

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-129512?

Upgrade log4net to 3.6.0 or later.

## Is CVE-2026-129512 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129512 is a medium-severity vulnerability in Apache log4net, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129512 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-129512/ (Markdown: https://insights.sbomify.com/CVE-2026-129512/index.md)
```

## Sources

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

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