{
  "_class" : "io.jenkins.plugins.analysis.core.restapi.ReportApi",
  "issues" : [
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-core-2.25.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayConsole.war/WEB-INF/lib/log4j-core-2.25.3.jar",
      "fingerprint" : "FALLBACK-6610c7f6",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-34480: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j Core's XmlLayout fails to sanitize characters\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34480**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|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)|\u000a\u000aApache 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.\u000a\u000aThe impact depends on the StAX implementation in use:\u000a\u000a  *  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.\u000a  *  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.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34480\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1398",
      "severity" : "NORMAL",
      "toString" : "log4j-core-2.25.3.jar(1,0): CVE-2026-34480: : CVE-2026-34480: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j Core's XmlLayout fails to sanitize characters\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34480**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|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)|\u000a\u000aApache 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.\u000a\u000aThe impact depends on the StAX implementation in use:\u000a\u000a  *  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.\u000a  *  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.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34480\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)",
      "type" : "CVE-2026-34480"
    }
  ],
  "size" : 1,
  "toString" : "1 warning (normal: 1)"
}