CVE-2026-129512

Apache log4net: AdoNetAppender loses an event whose text the database cannot store

Published Nov 17, 2026 CVSS 3.1 · 5.3 Medium EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The flaw is an Improper Neutralization of Null Byte in Apache log4net’s AdoNetAppender. Unfiltered text parameters can carry a NUL character or an unpaired UTF‑16 surrogate to the database. If the database, such as PostgreSQL, rejects that value then the log event is discarded, and only the first such loss per appender is reported. An attacker who can inject log content containing these characters can therefore cause application activity to vanish from logs and potentially hide malicious action.

Affected Systems

Apache Software Foundation’s log4net log aggregator, from version 1.2.9 through just before 3.6.0, is vulnerable when the AdoNetAppender writes to relational databases. All deployments that use this component and target databases that reject NUL or surrogate values are susceptible.

Risk and Exploitability

The CVSS rating of 5.3 indicates moderate severity while the EPSS score is not available, so the probability of exploitation is presently unknown. The vulnerability is not listed in CISA’s KEV catalog, implying no recorded exploit activity. The likely attack vector depends on the application’s ability to accept user‑controlled log messages; an attacker feeding strings containing NUL or surrogate data can trigger log suppression and reduce auditability.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade log4net to version 3.6.0 or later, which contains the vendor fix for the AdoNetAppender.
  • Reconfigure the AdoNetAppender to sanitize or escape NUL and surrogate characters before binding them to the database, or replace it with a safer logging component.
  • If upgrading is not immediately possible, disable database logging for the affected appender or redirect logs to a destination that accepts NUL bytes, such as a plain‑text file.

Generated by OpenCVE AI on November 18, 2026 at 03:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
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.
Title Apache log4net: AdoNetAppender loses an event whose text the database cannot store
Weaknesses CWE-158
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Subscriptions

No data.

Weaknesses
  • CWE-158

    Improper Neutralization of Null Byte or NUL Character

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 18, 2026, 2:06 AM
Reserved
Nov 15, 2026, 8:28 PM
Status
Received
Published
Nov 17, 2026, 11:17 PM
Modified
Nov 18, 2026, 2:17 AM