Bug 2575550 (CVE-2026-129512) - CVE-2026-129512 log4net: log4net: Log event suppression via improper null byte handling in AdoNetAppender
Summary: CVE-2026-129512 log4net: log4net: Log event suppression via improper null byt...
Keywords:
Status: NEW
Alias: CVE-2026-129512
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2577151 2577152
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-17 22:22 UTC by OSIDB Bzimport
Modified: 2026-11-19 18:07 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-17 22:22:04 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.