Cyber ·
CVE-2026-129510: log4net, culture-sensitive CDATA end search hides later log events
A moderate flaw in Apache log4net's XmlLayout and XmlLayoutSchemaLog4J layouts can hide later log events when a message contains the CDATA end marker.
Source: advisory posted to the oss-sec feed on 17 November by Jan Friedrich, identified as CVE-2026-129510. Severity is moderate, with CVSS 3.1 score 5.3 (medium) and vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N. According to the text, the flaw affects Apache log4net from version 1.2.9 up to before 3.6.0, and also builds in the commit range 02e1e115435888485f2e28b414d267e39e799e07 up to 80d955e8c8f1e9f094c2b3d1c142147ee8b8b805. The description says both layouts split a message that contains the CDATA end marker, which can stop later events from being written. The available text is an automatic translation and is truncated, so it does not include the full fix details or all exploitation scenarios.
Relevance: this advisory concerns a .NET logging library, not an AI service. Rota Nacional does not patch log4net or replace updating the library. To address it, upgrade to an unaffected version as described in the official advisory.
If you use AI to study the alert or triage logs, do not paste production logs containing personal data without treatment. Before any model runs, the platform detects CPF, CNPJ, e-mail, phone numbers and person names and applies the organization's policy: placeholder markers, removal or a block. Usage metadata stays in the dashboard, and raw content stays only in an AES-256-GCM encrypted audit archive.
To verify the information, consult the original advisory through the official Apache project channel and compare the affected versions and commits with your own inventory before taking any action.