Skip to content
Fencer Intel
medium 5.3

CVE-2026-129512 json

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

published 5h ago modified 1h ago also EUVD-2026-128197

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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.

Patch / fix

  • Apache Software Foundation Apache log4net 3.6.0

Is CVE-2026-129512 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected products

  • Apache Software Foundation Apache log4net

Classification

Weakness
  • CWE-158 Improper Neutralization of Null Byte or NUL Character

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.