Log event suppression via forbidden XML characters
Published Apr 10, 2026 · Updated Apr 10, 2026
Improper output encoding in Apache Log4cxx before 1.7.0 allows attackers to suppress XMLLayout log records via forbidden XML characters. XMLLayout writes untrusted log messages and NDC and MDC property keys and values without removing characters forbidden by XML 1.0, producing documents that conforming parsers reject. Exploitation requires influence over logged data and can hide individual events from downstream indexing, impairing audit trails and detection.
Summary
What happened
Improper output encoding in Apache Log4cxx before 1.7.0 allows attackers to suppress XMLLayout log records via forbidden XML characters. XMLLayout writes untrusted log messages and NDC and MDC property keys and values without removing characters forbidden by XML 1.0, producing documents that conforming parsers reject. Exploitation requires influence over logged data and can hide individual events from downstream indexing, impairing audit trails and detection.
The record
- CVE
- CVE-2026-40023
- Published
- Apr 10, 2026
- Updated
- Apr 10, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Log4cxx
- Classifications
- CWE-116, T1562.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 2026CVE publishedPublication date reported by the CVE source.
- Apr 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo