CVE & CISA-KEV Catalog

CVE-2026-129511

MEDIUM
5.3
CVSS v3
NVD

Description

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.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityLow
AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploit Intelligence

0.41%probability of exploitation in 30 days
36thpercentile

Low risk: more likely to be exploited than 36% of all known CVEs.

References

Related Vulnerabilities

Other CWE-117 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2022-32549Medium5.32.5%--
CVE-2021-43410Medium5.32.4%-Fix
CVE-2019-14864Medium6.51.9%-Fix
CVE-2021-42250Medium6.51.8%-Fix
CVE-2024-47083High7.51.6%--
CVE-2025-54813High7.51.5%-Fix

Common questions

How do I fix CVE-2026-129511?

No published fix for CVE-2026-129511 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-129511 being actively exploited?

Not that we know of. CVE-2026-129511 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.41% is the estimated probability that it will be exploited in the next 30 days. That is higher than 36% of all scored CVEs.

How severe is CVE-2026-129511?

CVE-2026-129511 has a CVSS v3 base score of 5.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-129511
CVE-2026-129511 severity badge

Markdown

[![CVE-2026-129511](https://tridentstack.com/cve/badge/CVE-2026-129511.svg)](https://tridentstack.com/cve/CVE-2026-129511)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-129511"><img src="https://tridentstack.com/cve/badge/CVE-2026-129511.svg" alt="CVE-2026-129511"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

Run a free CVE scan on your fleetStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-18.