0--log4j-1.2-api-2.25.3.jar00-/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/log4j-1.2-api-2.25.3.jarFALLBACK-44bb7cff11CVE-2026-34479: LanguageSpecificPackageVulnerability The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to ... For additional help see: **Vulnerability CVE-2026-34479** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-1.2-api|2.25.4|[CVE-2026-34479](https://avd.aquasec.com/nvd/cve-2026-34479)| The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records. Two groups of users are affected: * Those using Log4j1XmlLayout directly in a Log4j Core 2 configuration file. * Those using the Log4j 1 configuration compatibility layer with org.apache.log4j.xml.XMLLayout specified as the layout class. Users are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version 2.25.4, which corrects this issue. Note: The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the Log4j 1 to Log4j 2 migration guide https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html , and specifically the section on eliminating reliance on the bridge. Package: org.apache.logging.log4j:log4j-1.2-api Installed Version: 2.25.3 Vulnerability CVE-2026-34479 Severity: MEDIUM Fixed Version: 2.25.4 Link: [CVE-2026-34479](https://avd.aquasec.com/nvd/cve-2026-34479)trivyTrivy Security Scanner-1444NORMALlog4j-1.2-api-2.25.3.jar(1,0): CVE-2026-34479: : CVE-2026-34479: LanguageSpecificPackageVulnerability The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to ... For additional help see: **Vulnerability CVE-2026-34479** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-1.2-api|2.25.4|[CVE-2026-34479](https://avd.aquasec.com/nvd/cve-2026-34479)| The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records. Two groups of users are affected: * Those using Log4j1XmlLayout directly in a Log4j Core 2 configuration file. * Those using the Log4j 1 configuration compatibility layer with org.apache.log4j.xml.XMLLayout specified as the layout class. Users are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version 2.25.4, which corrects this issue. Note: The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the Log4j 1 to Log4j 2 migration guide https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html , and specifically the section on eliminating reliance on the bridge. Package: org.apache.logging.log4j:log4j-1.2-api Installed Version: 2.25.3 Vulnerability CVE-2026-34479 Severity: MEDIUM Fixed Version: 2.25.4 Link: [CVE-2026-34479](https://avd.aquasec.com/nvd/cve-2026-34479)CVE-2026-3447911 warning (normal: 1)