AI Science Tracker

Apache log4net: Apache log4net: NUL character truncates OutputDebugStringAppender records

Apache log4net · AI involvement attributed to Claude Security

Finding and attribution

Improper Neutralization of Null Byte or NUL Character vulnerability in the OutputDebugStringAppender of Apache log4net. A NUL character in logged content ended the debug output record at that point, so everything the layout rendered after it, including exception text and trailing fields, was silently lost. A party whose data reaches a log message could hide the rest of that record. Only applications on Windows that use OutputDebugStringAppender are affected. This issue affects Apache log4net: fr

Product: Apache log4net. AI system: Claude Security. Team / organization: apache (CNA); AI attribution as credited in the CVE record.

CVE identifiers: CVE-2026-105240.

AI and human contribution (source account): The CNA record credits 'The Apache Software Foundation; Claude Security; Jan Friedrich'. It states the AI attribution as written there and does not describe the model's operation, autonomy or the human validation steps; none is inferred.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The CNA record establishes a coordinated disclosure with the credit above. It does not establish exploitation in the wild or a zero-day incident.

Remediation status: fix documented. CNA record links a fix commit or pull request; no fixed release version is stated in the record. Deployed patch status is not checked.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 6 Oct 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Medium · highest recorded score 5.3. Documented technical effects: Not available.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.

Documented fix: CNA record links a fix commit or pull request; no fixed release version is stated in the record. Deployed patch status is not checked.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases