# CVE-2026-129512 — Apache log4net

> As of 2026-11-18, CVE-2026-129512 is a MEDIUM-severity vulnerability in Apache log4net, CVSS v3.1 5.3, EPSS 0.4% (36.0th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-129512 as of 2026-11-18; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-18

## What is CVE-2026-129512?

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.

The record classifies CVE-2026-129512 under weakness class [CWE-158](https://intel.threadlinqs.com/cwe/CWE-158). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 2 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 5.3 — MEDIUM (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **EPSS (FIRST):** 0.4% probability of exploitation in the next 30 days, higher than 36.0% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-17

## Is CVE-2026-129512 being exploited?

It currently carries a trending score of 39 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [Apache Software Foundation](https://intel.threadlinqs.com/vendors/apache-software-foundation): Apache log4net

## How to fix CVE-2026-129512

Patch reference: [https://github.com/apache/logging-log4net/pull/355](https://github.com/apache/logging-log4net/pull/355). Vendor advisory: [https://lists.apache.org/thread.html/jgrh2z1l8tyk33ds6jp5ck18f7wckbch](https://lists.apache.org/thread.html/jgrh2z1l8tyk33ds6jp5ck18f7wckbch). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-129512

No threat campaign in the Threadlinqs corpus currently references CVE-2026-129512, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — patch](https://github.com/apache/logging-log4net/pull/355)
- [github.com — patch (a996aa8d569c709ddf0a5b1011a4f06bac9ce21d)](https://github.com/apache/logging-log4net/commit/a996aa8d569c709ddf0a5b1011a4f06bac9ce21d)
- [lists.apache.org — vendor advisory](https://lists.apache.org/thread.html/jgrh2z1l8tyk33ds6jp5ck18f7wckbch)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-129512
No Threadlinqs detection currently covers CVE-2026-129512; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
