Apache log4net up to 3.5.x FileAppender neutralization for logs

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00+ |
Summary
A vulnerability identified as problematic has been detected in Apache log4net up to 3.5.x. Affected by this issue is some unknown functionality of the component FileAppender/RollingFileAppender/UdpAppender/SmtpAppender. This manipulation causes neutralization for logs. The identification of this vulnerability is CVE-2026-129511. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability classified as problematic was found in Apache log4net up to 3.5.x. Affected by this vulnerability is some unknown functionality of the component FileAppender/RollingFileAppender/UdpAppender/SmtpAppender. The manipulation with an unknown input leads to a neutralization for logs vulnerability. The CWE definition for the vulnerability is CWE-117. The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file. As an impact it is known to affect integrity. The summary by CVE is:
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 advisory is shared at github.com. This vulnerability is known as CVE-2026-129511 since 11/15/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/17/2026).
Upgrading to version 3.6.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (apache): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Neutralization for logsCWE: CWE-117 / CWE-116 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: log4net 3.6.0
Timeline
11/15/2026 CVE reserved11/17/2026 Advisory disclosed
11/17/2026 VulDB entry created
11/17/2026 VulDB entry last update
Sources
Vendor: apache.orgAdvisory: github.com
Status: Confirmed
CNA: apache
CVE: CVE-2026-129511 (🔒)
GCVE (CVE): GCVE-0-2026-129511
GCVE (VulDB): GCVE-100-438769
Entry
Created: 11/17/2026 23:48Changes: 11/17/2026 23:48 (64)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.