{“lastseen”:””,”description”:”Apache Log4net’s XmlLayout https:\/\/logging.apache.org\/log4net\/manual\/configuration\/layouts.html#layout-list and XmlLayoutSchemaLog4J https:\/\/logging.apache.org\/log4net\/manual\/configuration\/layouts.html#layout-list , in versions before 3.3.0, fail to sanitize characters forbidden by the XML 1.0 specification https:\/\/www.w3.org\/TR\/xml\/#charsets in MDC property keys and values, as well as the identity field that may carry attacker-influenced data. This causes an exception during serialization and the silent loss of the affected log event.\\n\\nAn attacker who can influence any of these fields can exploit this to suppress individual log records, impairing audit trails and detection of malicious activity.\\n\\nUsers are advised to upgrade to Apache Log4net 3.3.0, which fixes this issue.”,”published”:”2026-04-10T15:44:17.451Z”,”modified”:”2026-04-10T17:35:01.228Z”,”type”:”cve”,”title”:”Apache Log4net: Silent log event loss in XmlLayout and XmlLayoutSchemaLog4J due to unescaped XML 1.0 forbidden characters”,”source”:”apache”,”references”:”https:\/\/github.com\/apache\/logging-log4net\/pull\/280\\nhttps:\/\/logging.apache.org\/security.html#CVE-2026-40021\\nhttps:\/\/logging.apache.org\/cyclonedx\/vdr.xml\\nhttps:\/\/logging.apache.org\/log4net\/manual\/configuration\/layouts.html\\nhttps:\/\/lists.apache.org\/thread\/q8otftjswhk69n3kxslqg7cobr0x4st7″,”id”:”CVE-2026-40021″,”bulletinFamily”:””,”cwe”:[“CWE-116″],”cvelist”:null,”sourceData”:”Apache Software Foundation Apache Log4net 0″,”sourceHref”:””,”cvss”:{“score”:6.3,”severity”:”MEDIUM”,”vector”:”CVSS:4.0\/AV:N\/AC:H\/AT:N\/PR:N\/UI:N\/VC:N\/VI:N\/VA:N\/SC:N\/SI:L\/SA:N”,”version”:”4.0″},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:””,”category_name”:”CVE”,”post_link”:””,”product”:”Apache Log4net”,”version”:”0″,”vendor”:”Apache Software Foundation”,”ai_description”:””,”ai_severity”:””,”ai_vendor”:””,”ai_product”:””,”ai_version”:””,”ai_score”:0}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:””,”description”:”Apache Log4net’s XmlLayout https:\/\/logging.apache.org\/log4net\/manual\/configuration\/layouts.html#layout-list and XmlLayoutSchemaLog4J https:\/\/logging.apache.org\/log4net\/manual\/configuration\/layouts.html#layout-list , in versions before 3.3.0, fail to sanitize characters forbidden by the XML 1.0 specification https:\/\/www.w3.org\/TR\/xml\/#charsets in MDC…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[6,8,23,12,21,13,7,11,5],"class_list":["post-42382","post","type-post","status-publish","format-standard","hentry","category-category_cve","tag-cve","tag-cvss","tag-cvss-63","tag-exploit","tag-medium","tag-news","tag-security","tag-tapic","tag-vulnerability"],"yoast_head":"\n