0--log4j-core-2.25.3.jar00-/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/log4j-core-2.25.3.jarFALLBACK-6610c7f611CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)trivyTrivy Security Scanner-1398NORMALlog4j-core-2.25.3.jar(1,0): CVE-2026-34480: : CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)CVE-2026-3448011 warning (normal: 1)