Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-129511Published 2026-11-17

CVE-2026-129511 — Apache log4net

medium

As of 2026-11-18, CVE-2026-129511 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-129511 as of 2026-11-18; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
5.3/10Medium
EPSS
0.4%Higher than 36.0% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
4.1/10Threadlinqs triage score
Published
Updated 2026-11-18
CVSS v3.1 5.3 (MEDIUM) · EPSS 0.4% (higher than 36.0% of all scored CVEs) · Priority 4.1/10 · Published 2026-11-17

Last updated:

What is CVE-2026-129511?

Improper Output Neutralization for Logs vulnerability in the FileAppender, RollingFileAppender, UdpAppender and SmtpAppender of Apache log4net. Characters the configured encoding could not represent were converted by that encoding's best-fit fallback, which turns fullwidth characters such as U+FF1C, U+FF1E and U+FF02 into and ". The conversion happened after XmlLayout or XmlLayoutSchemaLog4J had escaped the text, so a party whose data reaches a log message could forge complete log events in an XML log, for example a fake audit entry. On .NET Framework this needs no configuration where the ANSI code page is single-byte, since that is the default encoding; on .NET it needs a configured single-byte encoding such as ISO-8859-1. This is the best-fit conversion described by the WorstFit research. 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-129511 under weakness class CWE-117. 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-129511 being exploited?

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

Affected products and versions

How to fix CVE-2026-129511

Patch reference: https://github.com/apache/logging-log4net/pull/355. Vendor advisory: https://lists.apache.org/thread.html/v2oljwjcboxk0tvyy5v86o2fjlslx1zt. 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-129511

No threat campaign in the Threadlinqs corpus currently references CVE-2026-129511, 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