CVE-2026-40023: Apache Log4cxx · Improper Encoding or Escaping of Output
Affects Apache Log4cxxSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.7.0 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.7.0
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Apache Log4cxx and Apache Log4cxx (Conan) and Apache Log4cxx (Brew) and org.apache.logging.log4cxx/log4cxx to 1.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Log4cxx | Affected
| Fixed in
|
| Apache Software FoundationApache Log4cxx (Conan) | Affected
| Fixed in
|
| Apache Software FoundationApache Log4cxx (Brew) | Affected
| Fixed in
|
Mavenorg.apache.logging.log4cxx/log4cxxpkg:maven/org.apache.logging.log4cxx/log4cxxOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:apache:log4cxx:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade to Apache Log4cxx version 1.7.0, which addresses this issue by properly sanitizing forbidden XML characters in log output. No other official remediation or temporary fixes are documented. Patch status is not explicitly confirmed beyond the recommendation to upgrade; therefore, check the vendor advisory for the latest remediation guidance.
Description
Apache Log4cxx's XMLLayout https://logging.apache.org/log4cxx/1.7.0/classlog4cxx_1_1xml_1_1XMLLayout.html , in versions before 1.7.0, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets in log messages, NDC, and MDC property keys and values, producing invalid XML output. Conforming XML parsers must reject such documents with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records. An attacker who can influence logged data can exploit this to suppress individual log records, impairing audit trails and detection of malicious activity. Users are advised to upgrade to Apache Log4cxx 1.7.0, which fixes this issue.
References
- github.com/apache/logging-log4cxx/pull/609 (opens in a new tab)
- logging.apache.org/security.html (opens in a new tab)
- logging.apache.org/cyclonedx/vdr.xml (opens in a new tab)
- logging.apache.org/log4cxx/1.7.0/classlog4cxx_1_1xml_1_1XMLLayout.html (opens in a new tab)
- lists.apache.org/thread/y15cv3zblg3dfwr5vy6ddbnl4zyrzr8b (opens in a new tab)
- openwall.com/lists/oss-security/2026/04/10/12 (opens in a new tab)