{ "_class" : "io.jenkins.plugins.analysis.core.restapi.ReportApi", "issues" : [ { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-bc0adcb9", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-2673: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL TLS 1.3 server may choose unexpected key agreement group\u000a\u000aFor additional help see: **Vulnerability CVE-2026-2673**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)|\u000a\u000aIssue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected\u000apreferred key exchange group when its key exchange group configuration includes\u000athe default by using the 'DEFAULT' keyword.\u000a\u000aImpact summary: A less preferred key exchange may be used even when a more\u000apreferred group is supported by both client and server, if the group\u000awas not included among the client's initial predicated keyshares.\u000aThis will sometimes be the case with the new hybrid post-quantum groups,\u000aif the client chooses to defer their use until specifically requested by\u000athe server.\u000a\u000aIf an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to\u000ainterpolate the built-in default group list into its own configuration, perhaps\u000aadding or removing specific elements, then an implementation defect causes the\u000a'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups\u000awere treated as a single sufficiently secure 'tuple', with the server not\u000asending a Hello Retry Request (HRR) even when a group in a more preferred tuple\u000awas mutually supported.\u000a\u000aAs a result, the client and server might fail to negotiate a mutually supported\u000apost-quantum key agreement group, such as 'X25519MLKEM768', if the client's\u000aconfiguration results in only 'classical' groups (such as 'X25519' being the\u000aonly ones in the client's initial keyshare prediction).\u000a\u000aOpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS\u000a1.3 key agreement group on TLS servers. The old syntax had a single 'flat'\u000alist of groups, and treated all the supported groups as sufficiently secure.\u000aIf any of the keyshares predicted by the client were supported by the server\u000athe most preferred among these was selected, even if other groups supported by\u000athe client, but not included in the list of predicted keyshares would have been\u000amore preferred, if included.\u000a\u000aThe new syntax partitions the groups into distinct 'tuples' of roughly\u000aequivalent security. Within each tuple the most preferred group included among\u000athe client's predicted keyshares is chosen, but if the client supports a group\u000afrom a more preferred tuple, but did not predict any corresponding keyshares,\u000athe server will ask the client to retry the ClientHello (by issuing a Hello\u000aRetry Request or HRR) with the most preferred mutually supported group.\u000a\u000aThe above works as expected when the server's configuration uses the built-in\u000adefault group list, or explicitly defines its own list by directly defining the\u000avarious desired groups and group 'tuples'.\u000a\u000aNo OpenSSL FIPS modules are affected by this issue, the code in question lies\u000aoutside the FIPS boundary.\u000a\u000aOpenSSL 3.6 and 3.5 are vulnerable to this issue.\u000a\u000aOpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released.\u000aOpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released.\u000a\u000aOpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-2673\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-2673: : CVE-2026-2673: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL TLS 1.3 server may choose unexpected key agreement group\u000a\u000aFor additional help see: **Vulnerability CVE-2026-2673**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)|\u000a\u000aIssue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected\u000apreferred key exchange group when its key exchange group configuration includes\u000athe default by using the 'DEFAULT' keyword.\u000a\u000aImpact summary: A less preferred key exchange may be used even when a more\u000apreferred group is supported by both client and server, if the group\u000awas not included among the client's initial predicated keyshares.\u000aThis will sometimes be the case with the new hybrid post-quantum groups,\u000aif the client chooses to defer their use until specifically requested by\u000athe server.\u000a\u000aIf an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to\u000ainterpolate the built-in default group list into its own configuration, perhaps\u000aadding or removing specific elements, then an implementation defect causes the\u000a'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups\u000awere treated as a single sufficiently secure 'tuple', with the server not\u000asending a Hello Retry Request (HRR) even when a group in a more preferred tuple\u000awas mutually supported.\u000a\u000aAs a result, the client and server might fail to negotiate a mutually supported\u000apost-quantum key agreement group, such as 'X25519MLKEM768', if the client's\u000aconfiguration results in only 'classical' groups (such as 'X25519' being the\u000aonly ones in the client's initial keyshare prediction).\u000a\u000aOpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS\u000a1.3 key agreement group on TLS servers. The old syntax had a single 'flat'\u000alist of groups, and treated all the supported groups as sufficiently secure.\u000aIf any of the keyshares predicted by the client were supported by the server\u000athe most preferred among these was selected, even if other groups supported by\u000athe client, but not included in the list of predicted keyshares would have been\u000amore preferred, if included.\u000a\u000aThe new syntax partitions the groups into distinct 'tuples' of roughly\u000aequivalent security. Within each tuple the most preferred group included among\u000athe client's predicted keyshares is chosen, but if the client supports a group\u000afrom a more preferred tuple, but did not predict any corresponding keyshares,\u000athe server will ask the client to retry the ClientHello (by issuing a Hello\u000aRetry Request or HRR) with the most preferred mutually supported group.\u000a\u000aThe above works as expected when the server's configuration uses the built-in\u000adefault group list, or explicitly defines its own list by directly defining the\u000avarious desired groups and group 'tuples'.\u000a\u000aNo OpenSSL FIPS modules are affected by this issue, the code in question lies\u000aoutside the FIPS boundary.\u000a\u000aOpenSSL 3.6 and 3.5 are vulnerable to this issue.\u000a\u000aOpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released.\u000aOpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released.\u000a\u000aOpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-2673\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)", "type" : "CVE-2026-2673" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-bc0adcb9", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-2673: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL TLS 1.3 server may choose unexpected key agreement group\u000a\u000aFor additional help see: **Vulnerability CVE-2026-2673**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)|\u000a\u000aIssue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected\u000apreferred key exchange group when its key exchange group configuration includes\u000athe default by using the 'DEFAULT' keyword.\u000a\u000aImpact summary: A less preferred key exchange may be used even when a more\u000apreferred group is supported by both client and server, if the group\u000awas not included among the client's initial predicated keyshares.\u000aThis will sometimes be the case with the new hybrid post-quantum groups,\u000aif the client chooses to defer their use until specifically requested by\u000athe server.\u000a\u000aIf an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to\u000ainterpolate the built-in default group list into its own configuration, perhaps\u000aadding or removing specific elements, then an implementation defect causes the\u000a'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups\u000awere treated as a single sufficiently secure 'tuple', with the server not\u000asending a Hello Retry Request (HRR) even when a group in a more preferred tuple\u000awas mutually supported.\u000a\u000aAs a result, the client and server might fail to negotiate a mutually supported\u000apost-quantum key agreement group, such as 'X25519MLKEM768', if the client's\u000aconfiguration results in only 'classical' groups (such as 'X25519' being the\u000aonly ones in the client's initial keyshare prediction).\u000a\u000aOpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS\u000a1.3 key agreement group on TLS servers. The old syntax had a single 'flat'\u000alist of groups, and treated all the supported groups as sufficiently secure.\u000aIf any of the keyshares predicted by the client were supported by the server\u000athe most preferred among these was selected, even if other groups supported by\u000athe client, but not included in the list of predicted keyshares would have been\u000amore preferred, if included.\u000a\u000aThe new syntax partitions the groups into distinct 'tuples' of roughly\u000aequivalent security. Within each tuple the most preferred group included among\u000athe client's predicted keyshares is chosen, but if the client supports a group\u000afrom a more preferred tuple, but did not predict any corresponding keyshares,\u000athe server will ask the client to retry the ClientHello (by issuing a Hello\u000aRetry Request or HRR) with the most preferred mutually supported group.\u000a\u000aThe above works as expected when the server's configuration uses the built-in\u000adefault group list, or explicitly defines its own list by directly defining the\u000avarious desired groups and group 'tuples'.\u000a\u000aNo OpenSSL FIPS modules are affected by this issue, the code in question lies\u000aoutside the FIPS boundary.\u000a\u000aOpenSSL 3.6 and 3.5 are vulnerable to this issue.\u000a\u000aOpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released.\u000aOpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released.\u000a\u000aOpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-2673\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-2673: : CVE-2026-2673: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL TLS 1.3 server may choose unexpected key agreement group\u000a\u000aFor additional help see: **Vulnerability CVE-2026-2673**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)|\u000a\u000aIssue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected\u000apreferred key exchange group when its key exchange group configuration includes\u000athe default by using the 'DEFAULT' keyword.\u000a\u000aImpact summary: A less preferred key exchange may be used even when a more\u000apreferred group is supported by both client and server, if the group\u000awas not included among the client's initial predicated keyshares.\u000aThis will sometimes be the case with the new hybrid post-quantum groups,\u000aif the client chooses to defer their use until specifically requested by\u000athe server.\u000a\u000aIf an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to\u000ainterpolate the built-in default group list into its own configuration, perhaps\u000aadding or removing specific elements, then an implementation defect causes the\u000a'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups\u000awere treated as a single sufficiently secure 'tuple', with the server not\u000asending a Hello Retry Request (HRR) even when a group in a more preferred tuple\u000awas mutually supported.\u000a\u000aAs a result, the client and server might fail to negotiate a mutually supported\u000apost-quantum key agreement group, such as 'X25519MLKEM768', if the client's\u000aconfiguration results in only 'classical' groups (such as 'X25519' being the\u000aonly ones in the client's initial keyshare prediction).\u000a\u000aOpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS\u000a1.3 key agreement group on TLS servers. The old syntax had a single 'flat'\u000alist of groups, and treated all the supported groups as sufficiently secure.\u000aIf any of the keyshares predicted by the client were supported by the server\u000athe most preferred among these was selected, even if other groups supported by\u000athe client, but not included in the list of predicted keyshares would have been\u000amore preferred, if included.\u000a\u000aThe new syntax partitions the groups into distinct 'tuples' of roughly\u000aequivalent security. Within each tuple the most preferred group included among\u000athe client's predicted keyshares is chosen, but if the client supports a group\u000afrom a more preferred tuple, but did not predict any corresponding keyshares,\u000athe server will ask the client to retry the ClientHello (by issuing a Hello\u000aRetry Request or HRR) with the most preferred mutually supported group.\u000a\u000aThe above works as expected when the server's configuration uses the built-in\u000adefault group list, or explicitly defines its own list by directly defining the\u000avarious desired groups and group 'tuples'.\u000a\u000aNo OpenSSL FIPS modules are affected by this issue, the code in question lies\u000aoutside the FIPS boundary.\u000a\u000aOpenSSL 3.6 and 3.5 are vulnerable to this issue.\u000a\u000aOpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released.\u000aOpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released.\u000a\u000aOpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-2673\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)", "type" : "CVE-2026-2673" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-d29a4e25", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-28387: OsPackageVulnerability\u000a\u000aIssue summary: An uncommon configuration of clients performing DANE TL ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28387**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)|\u000a\u000aIssue summary: An uncommon configuration of clients performing DANE TLSA-based\u000aserver authentication, when paired with uncommon server DANE TLSA records, may\u000aresult in a use-after-free and/or double-free on the client side.\u000a\u000aImpact summary: A use after free can have a range of potential consequences\u000asuch as the corruption of valid data, crashes or execution of arbitrary code.\u000a\u000aHowever, the issue only affects clients that make use of TLSA records with both\u000athe PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate\u000ausage.\u000a\u000aBy far the most common deployment of DANE is in SMTP MTAs for which RFC7672\u000arecommends that clients treat as 'unusable' any TLSA records that have the PKIX\u000acertificate usages. These SMTP (or other similar) clients are not vulnerable\u000ato this issue. Conversely, any clients that support only the PKIX usages, and\u000aignore the DANE-TA(2) usage are also not vulnerable.\u000a\u000aThe client would also need to be communicating with a server that publishes a\u000aTLSA RRset with both types of TLSA records.\u000a\u000aNo FIPS modules are affected by this issue, the problem code is outside the\u000aFIPS module boundary.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28387\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-28387: : CVE-2026-28387: OsPackageVulnerability\u000a\u000aIssue summary: An uncommon configuration of clients performing DANE TL ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28387**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)|\u000a\u000aIssue summary: An uncommon configuration of clients performing DANE TLSA-based\u000aserver authentication, when paired with uncommon server DANE TLSA records, may\u000aresult in a use-after-free and/or double-free on the client side.\u000a\u000aImpact summary: A use after free can have a range of potential consequences\u000asuch as the corruption of valid data, crashes or execution of arbitrary code.\u000a\u000aHowever, the issue only affects clients that make use of TLSA records with both\u000athe PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate\u000ausage.\u000a\u000aBy far the most common deployment of DANE is in SMTP MTAs for which RFC7672\u000arecommends that clients treat as 'unusable' any TLSA records that have the PKIX\u000acertificate usages. These SMTP (or other similar) clients are not vulnerable\u000ato this issue. Conversely, any clients that support only the PKIX usages, and\u000aignore the DANE-TA(2) usage are also not vulnerable.\u000a\u000aThe client would also need to be communicating with a server that publishes a\u000aTLSA RRset with both types of TLSA records.\u000a\u000aNo FIPS modules are affected by this issue, the problem code is outside the\u000aFIPS module boundary.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28387\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)", "type" : "CVE-2026-28387" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-d29a4e25", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-28387: OsPackageVulnerability\u000a\u000aIssue summary: An uncommon configuration of clients performing DANE TL ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28387**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)|\u000a\u000aIssue summary: An uncommon configuration of clients performing DANE TLSA-based\u000aserver authentication, when paired with uncommon server DANE TLSA records, may\u000aresult in a use-after-free and/or double-free on the client side.\u000a\u000aImpact summary: A use after free can have a range of potential consequences\u000asuch as the corruption of valid data, crashes or execution of arbitrary code.\u000a\u000aHowever, the issue only affects clients that make use of TLSA records with both\u000athe PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate\u000ausage.\u000a\u000aBy far the most common deployment of DANE is in SMTP MTAs for which RFC7672\u000arecommends that clients treat as 'unusable' any TLSA records that have the PKIX\u000acertificate usages. These SMTP (or other similar) clients are not vulnerable\u000ato this issue. Conversely, any clients that support only the PKIX usages, and\u000aignore the DANE-TA(2) usage are also not vulnerable.\u000a\u000aThe client would also need to be communicating with a server that publishes a\u000aTLSA RRset with both types of TLSA records.\u000a\u000aNo FIPS modules are affected by this issue, the problem code is outside the\u000aFIPS module boundary.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28387\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-28387: : CVE-2026-28387: OsPackageVulnerability\u000a\u000aIssue summary: An uncommon configuration of clients performing DANE TL ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28387**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)|\u000a\u000aIssue summary: An uncommon configuration of clients performing DANE TLSA-based\u000aserver authentication, when paired with uncommon server DANE TLSA records, may\u000aresult in a use-after-free and/or double-free on the client side.\u000a\u000aImpact summary: A use after free can have a range of potential consequences\u000asuch as the corruption of valid data, crashes or execution of arbitrary code.\u000a\u000aHowever, the issue only affects clients that make use of TLSA records with both\u000athe PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate\u000ausage.\u000a\u000aBy far the most common deployment of DANE is in SMTP MTAs for which RFC7672\u000arecommends that clients treat as 'unusable' any TLSA records that have the PKIX\u000acertificate usages. These SMTP (or other similar) clients are not vulnerable\u000ato this issue. Conversely, any clients that support only the PKIX usages, and\u000aignore the DANE-TA(2) usage are also not vulnerable.\u000a\u000aThe client would also need to be communicating with a server that publishes a\u000aTLSA RRset with both types of TLSA records.\u000a\u000aNo FIPS modules are affected by this issue, the problem code is outside the\u000aFIPS module boundary.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28387\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)", "type" : "CVE-2026-28387" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-d2b6e716", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-28388: OsPackageVulnerability\u000a\u000aIssue summary: When a delta CRL that contains a Delta CRL Indicator ex ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28388**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)|\u000a\u000aIssue summary: When a delta CRL that contains a Delta CRL Indicator extension\u000ais processed a NULL pointer dereference might happen if the required CRL\u000aNumber extension is missing.\u000a\u000aImpact summary: A NULL pointer dereference can trigger a crash which\u000aleads to a Denial of Service for an application.\u000a\u000aWhen CRL processing and delta CRL processing is enabled during X.509\u000acertificate verification, the delta CRL processing does not check\u000awhether the CRL Number extension is NULL before dereferencing it.\u000aWhen a malformed delta CRL file is being processed, this parameter\u000acan be NULL, causing a NULL pointer dereference.\u000a\u000aExploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in\u000athe verification context, the certificate being verified to contain a\u000afreshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and\u000aan attacker to provide a malformed CRL to an application that processes it.\u000a\u000aThe vulnerability is limited to Denial of Service and cannot be escalated to\u000aachieve code execution or memory disclosure. For that reason the issue was\u000aassessed as Low severity according to our Security Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28388\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-28388: : CVE-2026-28388: OsPackageVulnerability\u000a\u000aIssue summary: When a delta CRL that contains a Delta CRL Indicator ex ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28388**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)|\u000a\u000aIssue summary: When a delta CRL that contains a Delta CRL Indicator extension\u000ais processed a NULL pointer dereference might happen if the required CRL\u000aNumber extension is missing.\u000a\u000aImpact summary: A NULL pointer dereference can trigger a crash which\u000aleads to a Denial of Service for an application.\u000a\u000aWhen CRL processing and delta CRL processing is enabled during X.509\u000acertificate verification, the delta CRL processing does not check\u000awhether the CRL Number extension is NULL before dereferencing it.\u000aWhen a malformed delta CRL file is being processed, this parameter\u000acan be NULL, causing a NULL pointer dereference.\u000a\u000aExploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in\u000athe verification context, the certificate being verified to contain a\u000afreshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and\u000aan attacker to provide a malformed CRL to an application that processes it.\u000a\u000aThe vulnerability is limited to Denial of Service and cannot be escalated to\u000aachieve code execution or memory disclosure. For that reason the issue was\u000aassessed as Low severity according to our Security Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28388\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)", "type" : "CVE-2026-28388" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-d2b6e716", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-28388: OsPackageVulnerability\u000a\u000aIssue summary: When a delta CRL that contains a Delta CRL Indicator ex ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28388**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)|\u000a\u000aIssue summary: When a delta CRL that contains a Delta CRL Indicator extension\u000ais processed a NULL pointer dereference might happen if the required CRL\u000aNumber extension is missing.\u000a\u000aImpact summary: A NULL pointer dereference can trigger a crash which\u000aleads to a Denial of Service for an application.\u000a\u000aWhen CRL processing and delta CRL processing is enabled during X.509\u000acertificate verification, the delta CRL processing does not check\u000awhether the CRL Number extension is NULL before dereferencing it.\u000aWhen a malformed delta CRL file is being processed, this parameter\u000acan be NULL, causing a NULL pointer dereference.\u000a\u000aExploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in\u000athe verification context, the certificate being verified to contain a\u000afreshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and\u000aan attacker to provide a malformed CRL to an application that processes it.\u000a\u000aThe vulnerability is limited to Denial of Service and cannot be escalated to\u000aachieve code execution or memory disclosure. For that reason the issue was\u000aassessed as Low severity according to our Security Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28388\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-28388: : CVE-2026-28388: OsPackageVulnerability\u000a\u000aIssue summary: When a delta CRL that contains a Delta CRL Indicator ex ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28388**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)|\u000a\u000aIssue summary: When a delta CRL that contains a Delta CRL Indicator extension\u000ais processed a NULL pointer dereference might happen if the required CRL\u000aNumber extension is missing.\u000a\u000aImpact summary: A NULL pointer dereference can trigger a crash which\u000aleads to a Denial of Service for an application.\u000a\u000aWhen CRL processing and delta CRL processing is enabled during X.509\u000acertificate verification, the delta CRL processing does not check\u000awhether the CRL Number extension is NULL before dereferencing it.\u000aWhen a malformed delta CRL file is being processed, this parameter\u000acan be NULL, causing a NULL pointer dereference.\u000a\u000aExploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in\u000athe verification context, the certificate being verified to contain a\u000afreshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and\u000aan attacker to provide a malformed CRL to an application that processes it.\u000a\u000aThe vulnerability is limited to Denial of Service and cannot be escalated to\u000aachieve code execution or memory disclosure. For that reason the issue was\u000aassessed as Low severity according to our Security Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28388\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)", "type" : "CVE-2026-28388" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-d2d38007", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-28389: OsPackageVulnerability\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData messag ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28389**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)|\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData message\u000awith KeyAgreeRecipientInfo a NULL pointer dereference can happen.\u000a\u000aImpact summary: Applications that process attacker-controlled CMS data may\u000acrash before authentication or cryptographic operations occur resulting in\u000aDenial of Service.\u000a\u000aWhen a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is\u000aprocessed, the optional parameters field of KeyEncryptionAlgorithmIdentifier\u000ais examined without checking for its presence. This results in a NULL\u000apointer dereference if the field is missing.\u000a\u000aApplications and services that call CMS_decrypt() on untrusted input\u000a(e.g., S/MIME processing or CMS-based protocols) are vulnerable.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28389\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-28389: : CVE-2026-28389: OsPackageVulnerability\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData messag ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28389**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)|\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData message\u000awith KeyAgreeRecipientInfo a NULL pointer dereference can happen.\u000a\u000aImpact summary: Applications that process attacker-controlled CMS data may\u000acrash before authentication or cryptographic operations occur resulting in\u000aDenial of Service.\u000a\u000aWhen a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is\u000aprocessed, the optional parameters field of KeyEncryptionAlgorithmIdentifier\u000ais examined without checking for its presence. This results in a NULL\u000apointer dereference if the field is missing.\u000a\u000aApplications and services that call CMS_decrypt() on untrusted input\u000a(e.g., S/MIME processing or CMS-based protocols) are vulnerable.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28389\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)", "type" : "CVE-2026-28389" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-d2d38007", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-28389: OsPackageVulnerability\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData messag ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28389**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)|\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData message\u000awith KeyAgreeRecipientInfo a NULL pointer dereference can happen.\u000a\u000aImpact summary: Applications that process attacker-controlled CMS data may\u000acrash before authentication or cryptographic operations occur resulting in\u000aDenial of Service.\u000a\u000aWhen a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is\u000aprocessed, the optional parameters field of KeyEncryptionAlgorithmIdentifier\u000ais examined without checking for its presence. This results in a NULL\u000apointer dereference if the field is missing.\u000a\u000aApplications and services that call CMS_decrypt() on untrusted input\u000a(e.g., S/MIME processing or CMS-based protocols) are vulnerable.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28389\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-28389: : CVE-2026-28389: OsPackageVulnerability\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData messag ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28389**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)|\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData message\u000awith KeyAgreeRecipientInfo a NULL pointer dereference can happen.\u000a\u000aImpact summary: Applications that process attacker-controlled CMS data may\u000acrash before authentication or cryptographic operations occur resulting in\u000aDenial of Service.\u000a\u000aWhen a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is\u000aprocessed, the optional parameters field of KeyEncryptionAlgorithmIdentifier\u000ais examined without checking for its presence. This results in a NULL\u000apointer dereference if the field is missing.\u000a\u000aApplications and services that call CMS_decrypt() on untrusted input\u000a(e.g., S/MIME processing or CMS-based protocols) are vulnerable.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28389\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)", "type" : "CVE-2026-28389" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-840d6efb", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-28390: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to NULL pointer dereference in CMS EnvelopedData processing\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28390**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libssl3|3.5.6-r0|[CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)|\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData message\u000awith KeyTransportRecipientInfo a NULL pointer dereference can happen.\u000a\u000aImpact summary: Applications that process attacker-controlled CMS data may\u000acrash before authentication or cryptographic operations occur resulting in\u000aDenial of Service.\u000a\u000aWhen a CMS EnvelopedData message that uses KeyTransportRecipientInfo with\u000aRSA-OAEP encryption is processed, the optional parameters field of\u000aRSA-OAEP SourceFunc algorithm identifier is examined without checking\u000afor its presence. This results in a NULL pointer dereference if the field\u000ais missing.\u000a\u000aApplications and services that call CMS_decrypt() on untrusted input\u000a(e.g., S/MIME processing or CMS-based protocols) are vulnerable.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28390\u000aSeverity: HIGH\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "govway(1,0): CVE-2026-28390: : CVE-2026-28390: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to NULL pointer dereference in CMS EnvelopedData processing\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28390**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libssl3|3.5.6-r0|[CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)|\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData message\u000awith KeyTransportRecipientInfo a NULL pointer dereference can happen.\u000a\u000aImpact summary: Applications that process attacker-controlled CMS data may\u000acrash before authentication or cryptographic operations occur resulting in\u000aDenial of Service.\u000a\u000aWhen a CMS EnvelopedData message that uses KeyTransportRecipientInfo with\u000aRSA-OAEP encryption is processed, the optional parameters field of\u000aRSA-OAEP SourceFunc algorithm identifier is examined without checking\u000afor its presence. This results in a NULL pointer dereference if the field\u000ais missing.\u000a\u000aApplications and services that call CMS_decrypt() on untrusted input\u000a(e.g., S/MIME processing or CMS-based protocols) are vulnerable.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28390\u000aSeverity: HIGH\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)", "type" : "CVE-2026-28390" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-840d6efb", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-28390: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to NULL pointer dereference in CMS EnvelopedData processing\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28390**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libssl3|3.5.6-r0|[CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)|\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData message\u000awith KeyTransportRecipientInfo a NULL pointer dereference can happen.\u000a\u000aImpact summary: Applications that process attacker-controlled CMS data may\u000acrash before authentication or cryptographic operations occur resulting in\u000aDenial of Service.\u000a\u000aWhen a CMS EnvelopedData message that uses KeyTransportRecipientInfo with\u000aRSA-OAEP encryption is processed, the optional parameters field of\u000aRSA-OAEP SourceFunc algorithm identifier is examined without checking\u000afor its presence. This results in a NULL pointer dereference if the field\u000ais missing.\u000a\u000aApplications and services that call CMS_decrypt() on untrusted input\u000a(e.g., S/MIME processing or CMS-based protocols) are vulnerable.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28390\u000aSeverity: HIGH\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "govway(1,0): CVE-2026-28390: : CVE-2026-28390: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to NULL pointer dereference in CMS EnvelopedData processing\u000a\u000aFor additional help see: **Vulnerability CVE-2026-28390**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libssl3|3.5.6-r0|[CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)|\u000a\u000aIssue summary: During processing of a crafted CMS EnvelopedData message\u000awith KeyTransportRecipientInfo a NULL pointer dereference can happen.\u000a\u000aImpact summary: Applications that process attacker-controlled CMS data may\u000acrash before authentication or cryptographic operations occur resulting in\u000aDenial of Service.\u000a\u000aWhen a CMS EnvelopedData message that uses KeyTransportRecipientInfo with\u000aRSA-OAEP encryption is processed, the optional parameters field of\u000aRSA-OAEP SourceFunc algorithm identifier is examined without checking\u000afor its presence. This results in a NULL pointer dereference if the field\u000ais missing.\u000a\u000aApplications and services that call CMS_decrypt() on untrusted input\u000a(e.g., S/MIME processing or CMS-based protocols) are vulnerable.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-28390\u000aSeverity: HIGH\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)", "type" : "CVE-2026-28390" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-7e2b0533", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-31789: OsPackageVulnerability\u000a\u000aIssue summary: Converting an excessively large OCTET STRING value to a ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-31789**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)|\u000a\u000aIssue summary: Converting an excessively large OCTET STRING value to\u000aa hexadecimal string leads to a heap buffer overflow on 32 bit platforms.\u000a\u000aImpact summary: A heap buffer overflow may lead to a crash or possibly\u000aan attacker controlled code execution or other undefined behavior.\u000a\u000aIf an attacker can supply a crafted X.509 certificate with an excessively\u000alarge OCTET STRING value in extensions such as the Subject Key Identifier\u000a(SKID) or Authority Key Identifier (AKID) which are being converted to hex,\u000athe size of the buffer needed for the result is calculated as multiplication\u000aof the input length by 3. On 32 bit platforms, this multiplication may overflow\u000aresulting in the allocation of a smaller buffer and a heap buffer overflow.\u000a\u000aApplications and services that print or log contents of untrusted X.509\u000acertificates are vulnerable to this issue. As the certificates would have\u000ato have sizes of over 1 Gigabyte, printing or logging such certificates\u000ais a fairly unlikely operation and only 32 bit platforms are affected,\u000athis issue was assigned Low severity.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-31789\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-31789: : CVE-2026-31789: OsPackageVulnerability\u000a\u000aIssue summary: Converting an excessively large OCTET STRING value to a ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-31789**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)|\u000a\u000aIssue summary: Converting an excessively large OCTET STRING value to\u000aa hexadecimal string leads to a heap buffer overflow on 32 bit platforms.\u000a\u000aImpact summary: A heap buffer overflow may lead to a crash or possibly\u000aan attacker controlled code execution or other undefined behavior.\u000a\u000aIf an attacker can supply a crafted X.509 certificate with an excessively\u000alarge OCTET STRING value in extensions such as the Subject Key Identifier\u000a(SKID) or Authority Key Identifier (AKID) which are being converted to hex,\u000athe size of the buffer needed for the result is calculated as multiplication\u000aof the input length by 3. On 32 bit platforms, this multiplication may overflow\u000aresulting in the allocation of a smaller buffer and a heap buffer overflow.\u000a\u000aApplications and services that print or log contents of untrusted X.509\u000acertificates are vulnerable to this issue. As the certificates would have\u000ato have sizes of over 1 Gigabyte, printing or logging such certificates\u000ais a fairly unlikely operation and only 32 bit platforms are affected,\u000athis issue was assigned Low severity.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-31789\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)", "type" : "CVE-2026-31789" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-7e2b0533", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-31789: OsPackageVulnerability\u000a\u000aIssue summary: Converting an excessively large OCTET STRING value to a ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-31789**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)|\u000a\u000aIssue summary: Converting an excessively large OCTET STRING value to\u000aa hexadecimal string leads to a heap buffer overflow on 32 bit platforms.\u000a\u000aImpact summary: A heap buffer overflow may lead to a crash or possibly\u000aan attacker controlled code execution or other undefined behavior.\u000a\u000aIf an attacker can supply a crafted X.509 certificate with an excessively\u000alarge OCTET STRING value in extensions such as the Subject Key Identifier\u000a(SKID) or Authority Key Identifier (AKID) which are being converted to hex,\u000athe size of the buffer needed for the result is calculated as multiplication\u000aof the input length by 3. On 32 bit platforms, this multiplication may overflow\u000aresulting in the allocation of a smaller buffer and a heap buffer overflow.\u000a\u000aApplications and services that print or log contents of untrusted X.509\u000acertificates are vulnerable to this issue. As the certificates would have\u000ato have sizes of over 1 Gigabyte, printing or logging such certificates\u000ais a fairly unlikely operation and only 32 bit platforms are affected,\u000athis issue was assigned Low severity.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-31789\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-31789: : CVE-2026-31789: OsPackageVulnerability\u000a\u000aIssue summary: Converting an excessively large OCTET STRING value to a ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-31789**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|LOW|libssl3|3.5.6-r0|[CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)|\u000a\u000aIssue summary: Converting an excessively large OCTET STRING value to\u000aa hexadecimal string leads to a heap buffer overflow on 32 bit platforms.\u000a\u000aImpact summary: A heap buffer overflow may lead to a crash or possibly\u000aan attacker controlled code execution or other undefined behavior.\u000a\u000aIf an attacker can supply a crafted X.509 certificate with an excessively\u000alarge OCTET STRING value in extensions such as the Subject Key Identifier\u000a(SKID) or Authority Key Identifier (AKID) which are being converted to hex,\u000athe size of the buffer needed for the result is calculated as multiplication\u000aof the input length by 3. On 32 bit platforms, this multiplication may overflow\u000aresulting in the allocation of a smaller buffer and a heap buffer overflow.\u000a\u000aApplications and services that print or log contents of untrusted X.509\u000acertificates are vulnerable to this issue. As the certificates would have\u000ato have sizes of over 1 Gigabyte, printing or logging such certificates\u000ais a fairly unlikely operation and only 32 bit platforms are affected,\u000athis issue was assigned Low severity.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the affected code is outside the OpenSSL FIPS module boundary.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-31789\u000aSeverity: LOW\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)", "type" : "CVE-2026-31789" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-51588824", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-31790: OsPackageVulnerability\u000a\u000aopenssl: openssl: Information Disclosure from Uninitialized Memory via Invalid RSA Public Key\u000a\u000aFor additional help see: **Vulnerability CVE-2026-31790**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.6-r0|[CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)|\u000a\u000aIssue summary: Applications using RSASVE key encapsulation to establish\u000aa secret encryption key can send contents of an uninitialized memory buffer to\u000aa malicious peer.\u000a\u000aImpact summary: The uninitialized buffer might contain sensitive data from the\u000aprevious execution of the application process which leads to sensitive data\u000aleakage to an attacker.\u000a\u000aRSA_public_encrypt() returns the number of bytes written on success and -1\u000aon error. The affected code tests only whether the return value is non-zero.\u000aAs a result, if RSA encryption fails, encapsulation can still return success to\u000athe caller, set the output lengths, and leave the caller to use the contents of\u000athe ciphertext buffer as if a valid KEM ciphertext had been produced.\u000a\u000aIf applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an\u000aattacker-supplied invalid RSA public key without first validating that key,\u000athen this may cause stale or uninitialized contents of the caller-provided\u000aciphertext buffer to be disclosed to the attacker in place of the KEM\u000aciphertext.\u000a\u000aAs a workaround calling EVP_PKEY_public_check() or\u000aEVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate\u000athe issue.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-31790\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "govway(1,0): CVE-2026-31790: : CVE-2026-31790: OsPackageVulnerability\u000a\u000aopenssl: openssl: Information Disclosure from Uninitialized Memory via Invalid RSA Public Key\u000a\u000aFor additional help see: **Vulnerability CVE-2026-31790**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.6-r0|[CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)|\u000a\u000aIssue summary: Applications using RSASVE key encapsulation to establish\u000aa secret encryption key can send contents of an uninitialized memory buffer to\u000aa malicious peer.\u000a\u000aImpact summary: The uninitialized buffer might contain sensitive data from the\u000aprevious execution of the application process which leads to sensitive data\u000aleakage to an attacker.\u000a\u000aRSA_public_encrypt() returns the number of bytes written on success and -1\u000aon error. The affected code tests only whether the return value is non-zero.\u000aAs a result, if RSA encryption fails, encapsulation can still return success to\u000athe caller, set the output lengths, and leave the caller to use the contents of\u000athe ciphertext buffer as if a valid KEM ciphertext had been produced.\u000a\u000aIf applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an\u000aattacker-supplied invalid RSA public key without first validating that key,\u000athen this may cause stale or uninitialized contents of the caller-provided\u000aciphertext buffer to be disclosed to the attacker in place of the KEM\u000aciphertext.\u000a\u000aAs a workaround calling EVP_PKEY_public_check() or\u000aEVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate\u000athe issue.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-31790\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)", "type" : "CVE-2026-31790" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-51588824", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-31790: OsPackageVulnerability\u000a\u000aopenssl: openssl: Information Disclosure from Uninitialized Memory via Invalid RSA Public Key\u000a\u000aFor additional help see: **Vulnerability CVE-2026-31790**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.6-r0|[CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)|\u000a\u000aIssue summary: Applications using RSASVE key encapsulation to establish\u000aa secret encryption key can send contents of an uninitialized memory buffer to\u000aa malicious peer.\u000a\u000aImpact summary: The uninitialized buffer might contain sensitive data from the\u000aprevious execution of the application process which leads to sensitive data\u000aleakage to an attacker.\u000a\u000aRSA_public_encrypt() returns the number of bytes written on success and -1\u000aon error. The affected code tests only whether the return value is non-zero.\u000aAs a result, if RSA encryption fails, encapsulation can still return success to\u000athe caller, set the output lengths, and leave the caller to use the contents of\u000athe ciphertext buffer as if a valid KEM ciphertext had been produced.\u000a\u000aIf applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an\u000aattacker-supplied invalid RSA public key without first validating that key,\u000athen this may cause stale or uninitialized contents of the caller-provided\u000aciphertext buffer to be disclosed to the attacker in place of the KEM\u000aciphertext.\u000a\u000aAs a workaround calling EVP_PKEY_public_check() or\u000aEVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate\u000athe issue.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-31790\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "govway(1,0): CVE-2026-31790: : CVE-2026-31790: OsPackageVulnerability\u000a\u000aopenssl: openssl: Information Disclosure from Uninitialized Memory via Invalid RSA Public Key\u000a\u000aFor additional help see: **Vulnerability CVE-2026-31790**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.6-r0|[CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)|\u000a\u000aIssue summary: Applications using RSASVE key encapsulation to establish\u000aa secret encryption key can send contents of an uninitialized memory buffer to\u000aa malicious peer.\u000a\u000aImpact summary: The uninitialized buffer might contain sensitive data from the\u000aprevious execution of the application process which leads to sensitive data\u000aleakage to an attacker.\u000a\u000aRSA_public_encrypt() returns the number of bytes written on success and -1\u000aon error. The affected code tests only whether the return value is non-zero.\u000aAs a result, if RSA encryption fails, encapsulation can still return success to\u000athe caller, set the output lengths, and leave the caller to use the contents of\u000athe ciphertext buffer as if a valid KEM ciphertext had been produced.\u000a\u000aIf applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an\u000aattacker-supplied invalid RSA public key without first validating that key,\u000athen this may cause stale or uninitialized contents of the caller-provided\u000aciphertext buffer to be disclosed to the attacker in place of the KEM\u000aciphertext.\u000a\u000aAs a workaround calling EVP_PKEY_public_check() or\u000aEVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate\u000athe issue.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.5-r0\u000aVulnerability CVE-2026-31790\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.6-r0\u000aLink: [CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)", "type" : "CVE-2026-31790" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-734c2411", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-34757: OsPackageVulnerability\u000a\u000aLIBPNG is a reference library for use in applications that read, creat ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34757**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|UNKNOWN|libpng|1.6.57-r0|[CVE-2026-34757](https://avd.aquasec.com/nvd/cve-2026-34757)|\u000a\u000aLIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.0.9 to before 1.6.57, passing a pointer obtained from png_get_PLTE, png_get_tRNS, or png_get_hIST back into the corresponding setter on the same png_struct/png_info pair causes the setter to read from freed memory and copy its contents into the replacement buffer. The setter frees the internal buffer before copying from the caller-supplied pointer, which now dangles. The freed region may contain stale data (producing silently corrupted chunk metadata) or data from subsequent heap allocations (leaking unrelated heap contents into the chunk struct). This vulnerability is fixed in 1.6.57.\u000a\u000aPackage: libpng\u000aInstalled Version: 1.6.56-r0\u000aVulnerability CVE-2026-34757\u000aSeverity: UNKNOWN\u000aFixed Version: 1.6.57-r0\u000aLink: [CVE-2026-34757](https://avd.aquasec.com/nvd/cve-2026-34757)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-34757: : CVE-2026-34757: OsPackageVulnerability\u000a\u000aLIBPNG is a reference library for use in applications that read, creat ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34757**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|UNKNOWN|libpng|1.6.57-r0|[CVE-2026-34757](https://avd.aquasec.com/nvd/cve-2026-34757)|\u000a\u000aLIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.0.9 to before 1.6.57, passing a pointer obtained from png_get_PLTE, png_get_tRNS, or png_get_hIST back into the corresponding setter on the same png_struct/png_info pair causes the setter to read from freed memory and copy its contents into the replacement buffer. The setter frees the internal buffer before copying from the caller-supplied pointer, which now dangles. The freed region may contain stale data (producing silently corrupted chunk metadata) or data from subsequent heap allocations (leaking unrelated heap contents into the chunk struct). This vulnerability is fixed in 1.6.57.\u000a\u000aPackage: libpng\u000aInstalled Version: 1.6.56-r0\u000aVulnerability CVE-2026-34757\u000aSeverity: UNKNOWN\u000aFixed Version: 1.6.57-r0\u000aLink: [CVE-2026-34757](https://avd.aquasec.com/nvd/cve-2026-34757)", "type" : "CVE-2026-34757" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-461d9acf", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-40200: OsPackageVulnerability\u000a\u000aAn issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-40200**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|UNKNOWN|musl-utils|1.2.5-r23|[CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)|\u000a\u000aAn issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based memory corruption can occur during qsort of very large arrays, due to incorrectly implemented double-word primitives. The number of elements must exceed about seven million, i.e., the 32nd Leonardo number on 32-bit platforms (or the 64th Leonardo number on 64-bit platforms, which is not practical).\u000a\u000aPackage: musl\u000aInstalled Version: 1.2.5-r21\u000aVulnerability CVE-2026-40200\u000aSeverity: UNKNOWN\u000aFixed Version: 1.2.5-r23\u000aLink: [CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-40200: : CVE-2026-40200: OsPackageVulnerability\u000a\u000aAn issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-40200**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|UNKNOWN|musl-utils|1.2.5-r23|[CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)|\u000a\u000aAn issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based memory corruption can occur during qsort of very large arrays, due to incorrectly implemented double-word primitives. The number of elements must exceed about seven million, i.e., the 32nd Leonardo number on 32-bit platforms (or the 64th Leonardo number on 64-bit platforms, which is not practical).\u000a\u000aPackage: musl\u000aInstalled Version: 1.2.5-r21\u000aVulnerability CVE-2026-40200\u000aSeverity: UNKNOWN\u000aFixed Version: 1.2.5-r23\u000aLink: [CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)", "type" : "CVE-2026-40200" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "govway", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/linkitaly/govway", "fingerprint" : "FALLBACK-461d9acf", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-40200: OsPackageVulnerability\u000a\u000aAn issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-40200**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|UNKNOWN|musl-utils|1.2.5-r23|[CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)|\u000a\u000aAn issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based memory corruption can occur during qsort of very large arrays, due to incorrectly implemented double-word primitives. The number of elements must exceed about seven million, i.e., the 32nd Leonardo number on 32-bit platforms (or the 64th Leonardo number on 64-bit platforms, which is not practical).\u000a\u000aPackage: musl-utils\u000aInstalled Version: 1.2.5-r21\u000aVulnerability CVE-2026-40200\u000aSeverity: UNKNOWN\u000aFixed Version: 1.2.5-r23\u000aLink: [CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "LOW", "toString" : "govway(1,0): CVE-2026-40200: : CVE-2026-40200: OsPackageVulnerability\u000a\u000aAn issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-40200**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|UNKNOWN|musl-utils|1.2.5-r23|[CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)|\u000a\u000aAn issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based memory corruption can occur during qsort of very large arrays, due to incorrectly implemented double-word primitives. The number of elements must exceed about seven million, i.e., the 32nd Leonardo number on 32-bit platforms (or the 64th Leonardo number on 64-bit platforms, which is not practical).\u000a\u000aPackage: musl-utils\u000aInstalled Version: 1.2.5-r21\u000aVulnerability CVE-2026-40200\u000aSeverity: UNKNOWN\u000aFixed Version: 1.2.5-r23\u000aLink: [CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)", "type" : "CVE-2026-40200" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "commons-lang-2.6.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/var/govway/batch/generatoreStatistiche/lib/commons-lang-2.6.jar", "fingerprint" : "FALLBACK-f48ad3a6", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "type" : "CVE-2025-48924" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "log4j-core-2.25.3.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/var/govway/batch/generatoreStatistiche/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" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "log4j-layout-template-json-2.25.3.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/var/govway/batch/generatoreStatistiche/lib/log4j-layout-template-json-2.25.3.jar", "fingerprint" : "FALLBACK-78a9f3ba", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "log4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "type" : "CVE-2026-34481" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "catalina.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/lib/catalina.jar", "fingerprint" : "FALLBACK-6a54c218", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-24880: LanguageSpecificPackageVulnerability\u000a\u000aInconsistent Interpretation of HTTP Requests ('HTTP Request/Response S ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-24880**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.52, 11.0.20|[CVE-2026-24880](https://avd.aquasec.com/nvd/cve-2026-24880)|\u000a\u000aInconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in Apache Tomcat via invalid chunk extension.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.1.0-M1 through 10.1.52, from 9.0.0.M1 through 9.0.115, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109.\u000aOther, unsupported versions may also be affected.\u000a\u000aUsers are recommended to upgrade to version 11.0.20, 10.1.52 or 9.0.116, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-24880\u000aSeverity: HIGH\u000aFixed Version: 9.0.116, 10.1.52, 11.0.20\u000aLink: [CVE-2026-24880](https://avd.aquasec.com/nvd/cve-2026-24880)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "catalina.jar(1,0): CVE-2026-24880: : CVE-2026-24880: LanguageSpecificPackageVulnerability\u000a\u000aInconsistent Interpretation of HTTP Requests ('HTTP Request/Response S ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-24880**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.52, 11.0.20|[CVE-2026-24880](https://avd.aquasec.com/nvd/cve-2026-24880)|\u000a\u000aInconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in Apache Tomcat via invalid chunk extension.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.1.0-M1 through 10.1.52, from 9.0.0.M1 through 9.0.115, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109.\u000aOther, unsupported versions may also be affected.\u000a\u000aUsers are recommended to upgrade to version 11.0.20, 10.1.52 or 9.0.116, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-24880\u000aSeverity: HIGH\u000aFixed Version: 9.0.116, 10.1.52, 11.0.20\u000aLink: [CVE-2026-24880](https://avd.aquasec.com/nvd/cve-2026-24880)", "type" : "CVE-2026-24880" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "catalina.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/lib/catalina.jar", "fingerprint" : "FALLBACK-82411fbb", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-25854: LanguageSpecificPackageVulnerability\u000a\u000aOccasional URL redirection to untrusted Site ('Open Redirect') vulnera ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-25854**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.53, 11.0.20|[CVE-2026-25854](https://avd.aquasec.com/nvd/cve-2026-25854)|\u000a\u000aOccasional URL redirection to untrusted Site ('Open Redirect') vulnerability in Apache Tomcat via the LoadBalancerDrainingValve.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.1.0-M1 through 10.1.52, from 9.0.0.M23 through 9.0.115, from 8.5.30 through 8.5.100.\u000aOther, unsupported versions may also be affected\u000a\u000aUsers are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-25854\u000aSeverity: MEDIUM\u000aFixed Version: 9.0.116, 10.1.53, 11.0.20\u000aLink: [CVE-2026-25854](https://avd.aquasec.com/nvd/cve-2026-25854)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "catalina.jar(1,0): CVE-2026-25854: : CVE-2026-25854: LanguageSpecificPackageVulnerability\u000a\u000aOccasional URL redirection to untrusted Site ('Open Redirect') vulnera ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-25854**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.53, 11.0.20|[CVE-2026-25854](https://avd.aquasec.com/nvd/cve-2026-25854)|\u000a\u000aOccasional URL redirection to untrusted Site ('Open Redirect') vulnerability in Apache Tomcat via the LoadBalancerDrainingValve.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.1.0-M1 through 10.1.52, from 9.0.0.M23 through 9.0.115, from 8.5.30 through 8.5.100.\u000aOther, unsupported versions may also be affected\u000a\u000aUsers are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-25854\u000aSeverity: MEDIUM\u000aFixed Version: 9.0.116, 10.1.53, 11.0.20\u000aLink: [CVE-2026-25854](https://avd.aquasec.com/nvd/cve-2026-25854)", "type" : "CVE-2026-25854" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "catalina.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/lib/catalina.jar", "fingerprint" : "FALLBACK-66a9e9cb", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-29129: LanguageSpecificPackageVulnerability\u000a\u000aConfigured cipher preference order not preserved vulnerability in Apac ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-29129**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.53, 11.0.20|[CVE-2026-29129](https://avd.aquasec.com/nvd/cve-2026-29129)|\u000a\u000aConfigured cipher preference order not preserved vulnerability in Apache Tomcat.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.16 through 11.0.18, from 10.1.51 through 10.1.52, from 9.0.114 through 9.0.115.\u000a\u000aUsers are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-29129\u000aSeverity: HIGH\u000aFixed Version: 9.0.116, 10.1.53, 11.0.20\u000aLink: [CVE-2026-29129](https://avd.aquasec.com/nvd/cve-2026-29129)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "catalina.jar(1,0): CVE-2026-29129: : CVE-2026-29129: LanguageSpecificPackageVulnerability\u000a\u000aConfigured cipher preference order not preserved vulnerability in Apac ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-29129**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.53, 11.0.20|[CVE-2026-29129](https://avd.aquasec.com/nvd/cve-2026-29129)|\u000a\u000aConfigured cipher preference order not preserved vulnerability in Apache Tomcat.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.16 through 11.0.18, from 10.1.51 through 10.1.52, from 9.0.114 through 9.0.115.\u000a\u000aUsers are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-29129\u000aSeverity: HIGH\u000aFixed Version: 9.0.116, 10.1.53, 11.0.20\u000aLink: [CVE-2026-29129](https://avd.aquasec.com/nvd/cve-2026-29129)", "type" : "CVE-2026-29129" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "catalina.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/lib/catalina.jar", "fingerprint" : "FALLBACK-6d249065", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-29145: LanguageSpecificPackageVulnerability\u000a\u000aCLIENT_CERT authentication does not fail as expected for some scenario ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-29145**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.53, 11.0.20|[CVE-2026-29145](https://avd.aquasec.com/nvd/cve-2026-29145)|\u000a\u000aCLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled vulnerability in Apache Tomcat, Apache Tomcat Native.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.1.0-M7 through 10.1.52, from 9.0.83 through 9.0.115; Apache Tomcat Native: from 1.1.23 through 1.1.34, from 1.2.0 through 1.2.39, from 1.3.0 through 1.3.6, from 2.0.0 through 2.0.13.\u000a\u000aUsers are recommended to upgrade to version Tomcat Native 1.3.7 or 2.0.14 and Tomcat 11.0.20, 10.1.53 and 9.0.116, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-29145\u000aSeverity: CRITICAL\u000aFixed Version: 9.0.116, 10.1.53, 11.0.20\u000aLink: [CVE-2026-29145](https://avd.aquasec.com/nvd/cve-2026-29145)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "catalina.jar(1,0): CVE-2026-29145: : CVE-2026-29145: LanguageSpecificPackageVulnerability\u000a\u000aCLIENT_CERT authentication does not fail as expected for some scenario ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-29145**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.53, 11.0.20|[CVE-2026-29145](https://avd.aquasec.com/nvd/cve-2026-29145)|\u000a\u000aCLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled vulnerability in Apache Tomcat, Apache Tomcat Native.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.1.0-M7 through 10.1.52, from 9.0.83 through 9.0.115; Apache Tomcat Native: from 1.1.23 through 1.1.34, from 1.2.0 through 1.2.39, from 1.3.0 through 1.3.6, from 2.0.0 through 2.0.13.\u000a\u000aUsers are recommended to upgrade to version Tomcat Native 1.3.7 or 2.0.14 and Tomcat 11.0.20, 10.1.53 and 9.0.116, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-29145\u000aSeverity: CRITICAL\u000aFixed Version: 9.0.116, 10.1.53, 11.0.20\u000aLink: [CVE-2026-29145](https://avd.aquasec.com/nvd/cve-2026-29145)", "type" : "CVE-2026-29145" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "catalina.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/lib/catalina.jar", "fingerprint" : "FALLBACK-6d412956", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-29146: LanguageSpecificPackageVulnerability\u000a\u000aPadding Oracle vulnerability in Apache Tomcat's EncryptInterceptor wit ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-29146**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.53, 11.0.19|[CVE-2026-29146](https://avd.aquasec.com/nvd/cve-2026-29146)|\u000a\u000aPadding Oracle vulnerability in Apache Tomcat's EncryptInterceptor with default configuration.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.0.0-M1 through 10.1.52, from 9.0.13 through 9..115, from 8.5.38 through 8.5.100, from 7.0.100 through 7.0.109.\u000a\u000aUsers are recommended to upgrade to version 11.0.19, 10.1.53 and 9.0.116, which fixes the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-29146\u000aSeverity: HIGH\u000aFixed Version: 9.0.116, 10.1.53, 11.0.19\u000aLink: [CVE-2026-29146](https://avd.aquasec.com/nvd/cve-2026-29146)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "catalina.jar(1,0): CVE-2026-29146: : CVE-2026-29146: LanguageSpecificPackageVulnerability\u000a\u000aPadding Oracle vulnerability in Apache Tomcat's EncryptInterceptor wit ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-29146**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.53, 11.0.19|[CVE-2026-29146](https://avd.aquasec.com/nvd/cve-2026-29146)|\u000a\u000aPadding Oracle vulnerability in Apache Tomcat's EncryptInterceptor with default configuration.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.0.0-M1 through 10.1.52, from 9.0.13 through 9..115, from 8.5.38 through 8.5.100, from 7.0.100 through 7.0.109.\u000a\u000aUsers are recommended to upgrade to version 11.0.19, 10.1.53 and 9.0.116, which fixes the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-29146\u000aSeverity: HIGH\u000aFixed Version: 9.0.116, 10.1.53, 11.0.19\u000aLink: [CVE-2026-29146](https://avd.aquasec.com/nvd/cve-2026-29146)", "type" : "CVE-2026-29146" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "catalina.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/lib/catalina.jar", "fingerprint" : "FALLBACK-f899c988", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-32990: LanguageSpecificPackageVulnerability\u000a\u000aImproper Input Validation vulnerability in Apache Tomcat due to an inc ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-32990**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.53, 11.0.20|[CVE-2026-32990](https://avd.aquasec.com/nvd/cve-2026-32990)|\u000a\u000aImproper Input Validation vulnerability in Apache Tomcat due to an incomplete fix of CVE-2025-66614.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.15 through 11.0.19, from 10.1.50 through 10.1.52, from 9.0.113 through 9.0.115.\u000a\u000aUsers are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-32990\u000aSeverity: MEDIUM\u000aFixed Version: 9.0.116, 10.1.53, 11.0.20\u000aLink: [CVE-2026-32990](https://avd.aquasec.com/nvd/cve-2026-32990)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "catalina.jar(1,0): CVE-2026-32990: : CVE-2026-32990: LanguageSpecificPackageVulnerability\u000a\u000aImproper Input Validation vulnerability in Apache Tomcat due to an inc ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-32990**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.53, 11.0.20|[CVE-2026-32990](https://avd.aquasec.com/nvd/cve-2026-32990)|\u000a\u000aImproper Input Validation vulnerability in Apache Tomcat due to an incomplete fix of CVE-2025-66614.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.15 through 11.0.19, from 10.1.50 through 10.1.52, from 9.0.113 through 9.0.115.\u000a\u000aUsers are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-32990\u000aSeverity: MEDIUM\u000aFixed Version: 9.0.116, 10.1.53, 11.0.20\u000aLink: [CVE-2026-32990](https://avd.aquasec.com/nvd/cve-2026-32990)", "type" : "CVE-2026-32990" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "catalina.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/lib/catalina.jar", "fingerprint" : "FALLBACK-ba96c298", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-34483: LanguageSpecificPackageVulnerability\u000a\u000aImproper Encoding or Escaping of Output vulnerability in the JsonAcces ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34483**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.54, 11.0.21|[CVE-2026-34483](https://avd.aquasec.com/nvd/cve-2026-34483)|\u000a\u000aImproper Encoding or Escaping of Output vulnerability in the JsonAccessLogValve component of Apache Tomcat.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.20, from 10.1.0-M1 through 10.1.53, from 9.0.40 through 9.0.116.\u000a\u000aUsers are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117 , which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-34483\u000aSeverity: HIGH\u000aFixed Version: 9.0.116, 10.1.54, 11.0.21\u000aLink: [CVE-2026-34483](https://avd.aquasec.com/nvd/cve-2026-34483)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "catalina.jar(1,0): CVE-2026-34483: : CVE-2026-34483: LanguageSpecificPackageVulnerability\u000a\u000aImproper Encoding or Escaping of Output vulnerability in the JsonAcces ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34483**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.tomcat:tomcat-catalina|9.0.116, 10.1.54, 11.0.21|[CVE-2026-34483](https://avd.aquasec.com/nvd/cve-2026-34483)|\u000a\u000aImproper Encoding or Escaping of Output vulnerability in the JsonAccessLogValve component of Apache Tomcat.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.20, from 10.1.0-M1 through 10.1.53, from 9.0.40 through 9.0.116.\u000a\u000aUsers are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117 , which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-34483\u000aSeverity: HIGH\u000aFixed Version: 9.0.116, 10.1.54, 11.0.21\u000aLink: [CVE-2026-34483](https://avd.aquasec.com/nvd/cve-2026-34483)", "type" : "CVE-2026-34483" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "catalina.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/lib/catalina.jar", "fingerprint" : "FALLBACK-bb09265c", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-34487: LanguageSpecificPackageVulnerability\u000a\u000aInsertion of Sensitive Information into Log File vulnerability in the ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34487**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.tomcat:tomcat-catalina|9.0.117, 10.1.54, 11.0.21|[CVE-2026-34487](https://avd.aquasec.com/nvd/cve-2026-34487)|\u000a\u000aInsertion of Sensitive Information into Log File vulnerability in the cloud membership for clustering component of Apache Tomcat exposed the Kubernetes bearer token.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.20, from 10.1.0-M1 through 10.1.53, from 9.0.13 through 9.0.116.\u000a\u000aUsers are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-34487\u000aSeverity: HIGH\u000aFixed Version: 9.0.117, 10.1.54, 11.0.21\u000aLink: [CVE-2026-34487](https://avd.aquasec.com/nvd/cve-2026-34487)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "catalina.jar(1,0): CVE-2026-34487: : CVE-2026-34487: LanguageSpecificPackageVulnerability\u000a\u000aInsertion of Sensitive Information into Log File vulnerability in the ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34487**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.tomcat:tomcat-catalina|9.0.117, 10.1.54, 11.0.21|[CVE-2026-34487](https://avd.aquasec.com/nvd/cve-2026-34487)|\u000a\u000aInsertion of Sensitive Information into Log File vulnerability in the cloud membership for clustering component of Apache Tomcat exposed the Kubernetes bearer token.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.20, from 10.1.0-M1 through 10.1.53, from 9.0.13 through 9.0.116.\u000a\u000aUsers are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fix the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-34487\u000aSeverity: HIGH\u000aFixed Version: 9.0.117, 10.1.54, 11.0.21\u000aLink: [CVE-2026-34487](https://avd.aquasec.com/nvd/cve-2026-34487)", "type" : "CVE-2026-34487" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "catalina.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/lib/catalina.jar", "fingerprint" : "FALLBACK-2bda82fb", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-34500: LanguageSpecificPackageVulnerability\u000a\u000aCLIENT_CERT authentication does not fail as expected for some scenario ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34500**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.tomcat:tomcat-catalina|9.0.117, 10.1.54, 11.0.21|[CVE-2026-34500](https://avd.aquasec.com/nvd/cve-2026-34500)|\u000a\u000aCLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled and FFM is used in Apache Tomcat.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M14 through 11.0.20, from 10.1.22 through 10.1.53, from 9.0.92 through 9.0.116.\u000a\u000aUsers are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fixes the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-34500\u000aSeverity: MEDIUM\u000aFixed Version: 9.0.117, 10.1.54, 11.0.21\u000aLink: [CVE-2026-34500](https://avd.aquasec.com/nvd/cve-2026-34500)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "catalina.jar(1,0): CVE-2026-34500: : CVE-2026-34500: LanguageSpecificPackageVulnerability\u000a\u000aCLIENT_CERT authentication does not fail as expected for some scenario ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34500**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.tomcat:tomcat-catalina|9.0.117, 10.1.54, 11.0.21|[CVE-2026-34500](https://avd.aquasec.com/nvd/cve-2026-34500)|\u000a\u000aCLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled and FFM is used in Apache Tomcat.\u000a\u000aThis issue affects Apache Tomcat: from 11.0.0-M14 through 11.0.20, from 10.1.22 through 10.1.53, from 9.0.92 through 9.0.116.\u000a\u000aUsers are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fixes the issue.\u000a\u000aPackage: org.apache.tomcat:tomcat-catalina\u000aInstalled Version: 9.0.115\u000aVulnerability CVE-2026-34500\u000aSeverity: MEDIUM\u000aFixed Version: 9.0.117, 10.1.54, 11.0.21\u000aLink: [CVE-2026-34500](https://avd.aquasec.com/nvd/cve-2026-34500)", "type" : "CVE-2026-34500" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "commons-lang-2.6.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govway.war/WEB-INF/lib/commons-lang-2.6.jar", "fingerprint" : "FALLBACK-f48ad3a6", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "type" : "CVE-2025-48924" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "hazelcast-5.3.8.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govway.war/WEB-INF/lib/hazelcast-5.3.8.jar", "fingerprint" : "FALLBACK-4e8e6257", "lineEnd" : 1, "lineStart" : 1, "message" : "GHSA-72hv-8253-57qq: LanguageSpecificPackageVulnerability\u000a\u000ajackson-core: Number Length Constraint Bypass in Async Parser Leads to Potential DoS Condition\u000a\u000aFor additional help see: **Vulnerability GHSA-72hv-8253-57qq**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|com.fasterxml.jackson.core:jackson-core|2.21.1, 2.18.6|[GHSA-72hv-8253-57qq](https://github.com/advisories/GHSA-72hv-8253-57qq)|\u000a\u000a### Summary\u000aThe non-blocking (async) JSON parser in `jackson-core` bypasses the `maxNumberLength` constraint (default: 1000 characters) defined in `StreamReadConstraints`. This allows an attacker to send JSON with arbitrarily long numbers through the async parser API, leading to excessive memory allocation and potential CPU exhaustion, resulting in a Denial of Service (DoS).\u000a\u000aThe standard synchronous parser correctly enforces this limit, but the async parser fails to do so, creating an inconsistent enforcement policy.\u000a\u000a### Details\u000aThe root cause is that the async parsing path in `NonBlockingUtf8JsonParserBase` (and related classes) does not call the methods responsible for number length validation.\u000a\u000a- The number parsing methods (e.g., `_finishNumberIntegralPart`) accumulate digits into the `TextBuffer` without any length checks.\u000a- After parsing, they call `_valueComplete()`, which finalizes the token but does **not** call `resetInt()` or `resetFloat()`.\u000a- The `resetInt()`/`resetFloat()` methods in `ParserBase` are where the `validateIntegerLength()` and `validateFPLength()` checks are performed.\u000a- Because this validation step is skipped, the `maxNumberLength` constraint is never enforced in the async code path.\u000a\u000a### PoC\u000aThe following JUnit 5 test demonstrates the vulnerability. It shows that the async parser accepts a 5,000-digit number, whereas the limit should be 1,000.\u000a\u000a```java\u000apackage tools.jackson.core.unittest.dos;\u000a\u000aimport java.nio.charset.StandardCharsets;\u000a\u000aimport org.junit.jupiter.api.Test;\u000a\u000aimport tools.jackson.core.*;\u000aimport tools.jackson.core.exc.StreamConstraintsException;\u000aimport tools.jackson.core.json.JsonFactory;\u000aimport tools.jackson.core.json.async.NonBlockingByteArrayJsonParser;\u000a\u000aimport static org.junit.jupiter.api.Assertions.*;\u000a\u000a/**\u000a * POC: Number Length Constraint Bypass in Non-Blocking (Async) JSON Parsers\u000a *\u000a * Authors: sprabhav7, rohan-repos\u000a * \u000a * maxNumberLength default = 1000 characters (digits).\u000a * A number with more than 1000 digits should be rejected by any parser.\u000a *\u000a * BUG: The async parser never calls resetInt()/resetFloat() which is where\u000a * validateIntegerLength()/validateFPLength() lives. Instead it calls\u000a * _valueComplete() which skips all number length validation.\u000a *\u000a * CWE-770: Allocation of Resources Without Limits or Throttling\u000a */\u000aclass AsyncParserNumberLengthBypassTest {\u000a\u000a private static final int MAX_NUMBER_LENGTH = 1000;\u000a private static final int TEST_NUMBER_LENGTH = 5000;\u000a\u000a private final JsonFactory factory = new JsonFactory();\u000a\u000a // CONTROL: Sync parser correctly rejects a number exceeding maxNumberLength\u000a @Test\u000a void syncParserRejectsLongNumber() throws Exception {\u000a byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH);\u000a\u0009\u0009\u000a\u0009\u0009// Output to console\u000a System.out.println(\"[SYNC] Parsing \" + TEST_NUMBER_LENGTH + \"-digit number (limit: \" + MAX_NUMBER_LENGTH + \")\");\u000a try {\u000a try (JsonParser p = factory.createParser(ObjectReadContext.empty(), payload)) {\u000a while (p.nextToken() != null) {\u000a if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) {\u000a System.out.println(\"[SYNC] Accepted number with \" + p.getText().length() + \" digits — UNEXPECTED\");\u000a }\u000a }\u000a }\u000a fail(\"Sync parser must reject a \" + TEST_NUMBER_LENGTH + \"-digit number\");\u000a } catch (StreamConstraintsException e) {\u000a System.out.println(\"[SYNC] Rejected with StreamConstraintsException: \" + e.getMessage());\u000a }\u000a }\u000a\u000a // VULNERABILITY: Async parser accepts the SAME number that sync rejects\u000a @Test\u000a void asyncParserAcceptsLongNumber() throws Exception {\u000a byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH);\u000a\u000a NonBlockingByteArrayJsonParser p =\u000a (NonBlockingByteArrayJsonParser) factory.createNonBlockingByteArrayParser(ObjectReadContext.empty());\u000a p.feedInput(payload, 0, payload.length);\u000a p.endOfInput();\u000a\u000a boolean foundNumber = false;\u000a try {\u000a while (p.nextToken() != null) {\u000a if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) {\u000a foundNumber = true;\u000a String numberText = p.getText();\u000a assertEquals(TEST_NUMBER_LENGTH, numberText.length(),\u000a \"Async parser silently accepted all \" + TEST_NUMBER_LENGTH + \" digits\");\u000a }\u000a }\u000a // Output to console\u000a System.out.println(\"[ASYNC INT] Accepted number with \" + TEST_NUMBER_LENGTH + \" digits — BUG CONFIRMED\");\u000a assertTrue(foundNumber, \"Parser should have produced a VALUE_NUMBER_INT token\");\u000a } catch (StreamConstraintsException e) {\u000a fail(\"Bug is fixed — async parser now correctly rejects long numbers: \" + e.getMessage());\u000a }\u000a p.close();\u000a }\u000a\u000a private byte[] buildPayloadWithLongInteger(int numDigits) {\u000a StringBuilder sb = new StringBuilder(numDigits + 10);\u000a sb.append(\"{\\\"v\\\":\");\u000a for (int i = 0; i < numDigits; i++) {\u000a sb.append((char) ('1' + (i % 9)));\u000a }\u000a sb.append('}');\u000a return sb.toString().getBytes(StandardCharsets.UTF_8);\u000a }\u000a}\u000a\u000a```\u000a\u000a\u000a### Impact\u000aA malicious actor can send a JSON document with an arbitrarily long number to an application using the async parser (e.g., in a Spring WebFlux or other reactive application). This can cause:\u000a1. **Memory Exhaustion:** Unbounded allocation of memory in the `TextBuffer` to store the number's digits, leading to an `OutOfMemoryError`.\u000a2. **CPU Exhaustion:** If the application subsequently calls `getBigIntegerValue()` or `getDecimalValue()`, the JVM can be tied up in O(n^2) `BigInteger` parsing operations, leading to a CPU-based DoS.\u000a\u000a### Suggested Remediation\u000a\u000aThe async parsing path should be updated to respect the `maxNumberLength` constraint. The simplest fix appears to ensure that `_valueComplete()` or a similar method in the async path calls the appropriate validation methods (`resetInt()` or `resetFloat()`) already present in `ParserBase`, mirroring the behavior of the synchronous parsers.\u000a\u000a**NOTE:** This research was performed in collaboration with [rohan-repos](https://github.com/rohan-repos)\u000a\u000aPackage: com.fasterxml.jackson.core:jackson-core\u000aInstalled Version: 2.15.2\u000aVulnerability GHSA-72hv-8253-57qq\u000aSeverity: MEDIUM\u000aFixed Version: 2.21.1, 2.18.6\u000aLink: [GHSA-72hv-8253-57qq](https://github.com/advisories/GHSA-72hv-8253-57qq)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "hazelcast-5.3.8.jar(1,0): GHSA-72hv-8253-57qq: : GHSA-72hv-8253-57qq: LanguageSpecificPackageVulnerability\u000a\u000ajackson-core: Number Length Constraint Bypass in Async Parser Leads to Potential DoS Condition\u000a\u000aFor additional help see: **Vulnerability GHSA-72hv-8253-57qq**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|com.fasterxml.jackson.core:jackson-core|2.21.1, 2.18.6|[GHSA-72hv-8253-57qq](https://github.com/advisories/GHSA-72hv-8253-57qq)|\u000a\u000a### Summary\u000aThe non-blocking (async) JSON parser in `jackson-core` bypasses the `maxNumberLength` constraint (default: 1000 characters) defined in `StreamReadConstraints`. This allows an attacker to send JSON with arbitrarily long numbers through the async parser API, leading to excessive memory allocation and potential CPU exhaustion, resulting in a Denial of Service (DoS).\u000a\u000aThe standard synchronous parser correctly enforces this limit, but the async parser fails to do so, creating an inconsistent enforcement policy.\u000a\u000a### Details\u000aThe root cause is that the async parsing path in `NonBlockingUtf8JsonParserBase` (and related classes) does not call the methods responsible for number length validation.\u000a\u000a- The number parsing methods (e.g., `_finishNumberIntegralPart`) accumulate digits into the `TextBuffer` without any length checks.\u000a- After parsing, they call `_valueComplete()`, which finalizes the token but does **not** call `resetInt()` or `resetFloat()`.\u000a- The `resetInt()`/`resetFloat()` methods in `ParserBase` are where the `validateIntegerLength()` and `validateFPLength()` checks are performed.\u000a- Because this validation step is skipped, the `maxNumberLength` constraint is never enforced in the async code path.\u000a\u000a### PoC\u000aThe following JUnit 5 test demonstrates the vulnerability. It shows that the async parser accepts a 5,000-digit number, whereas the limit should be 1,000.\u000a\u000a```java\u000apackage tools.jackson.core.unittest.dos;\u000a\u000aimport java.nio.charset.StandardCharsets;\u000a\u000aimport org.junit.jupiter.api.Test;\u000a\u000aimport tools.jackson.core.*;\u000aimport tools.jackson.core.exc.StreamConstraintsException;\u000aimport tools.jackson.core.json.JsonFactory;\u000aimport tools.jackson.core.json.async.NonBlockingByteArrayJsonParser;\u000a\u000aimport static org.junit.jupiter.api.Assertions.*;\u000a\u000a/**\u000a * POC: Number Length Constraint Bypass in Non-Blocking (Async) JSON Parsers\u000a *\u000a * Authors: sprabhav7, rohan-repos\u000a * \u000a * maxNumberLength default = 1000 characters (digits).\u000a * A number with more than 1000 digits should be rejected by any parser.\u000a *\u000a * BUG: The async parser never calls resetInt()/resetFloat() which is where\u000a * validateIntegerLength()/validateFPLength() lives. Instead it calls\u000a * _valueComplete() which skips all number length validation.\u000a *\u000a * CWE-770: Allocation of Resources Without Limits or Throttling\u000a */\u000aclass AsyncParserNumberLengthBypassTest {\u000a\u000a private static final int MAX_NUMBER_LENGTH = 1000;\u000a private static final int TEST_NUMBER_LENGTH = 5000;\u000a\u000a private final JsonFactory factory = new JsonFactory();\u000a\u000a // CONTROL: Sync parser correctly rejects a number exceeding maxNumberLength\u000a @Test\u000a void syncParserRejectsLongNumber() throws Exception {\u000a byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH);\u000a\u0009\u0009\u000a\u0009\u0009// Output to console\u000a System.out.println(\"[SYNC] Parsing \" + TEST_NUMBER_LENGTH + \"-digit number (limit: \" + MAX_NUMBER_LENGTH + \")\");\u000a try {\u000a try (JsonParser p = factory.createParser(ObjectReadContext.empty(), payload)) {\u000a while (p.nextToken() != null) {\u000a if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) {\u000a System.out.println(\"[SYNC] Accepted number with \" + p.getText().length() + \" digits — UNEXPECTED\");\u000a }\u000a }\u000a }\u000a fail(\"Sync parser must reject a \" + TEST_NUMBER_LENGTH + \"-digit number\");\u000a } catch (StreamConstraintsException e) {\u000a System.out.println(\"[SYNC] Rejected with StreamConstraintsException: \" + e.getMessage());\u000a }\u000a }\u000a\u000a // VULNERABILITY: Async parser accepts the SAME number that sync rejects\u000a @Test\u000a void asyncParserAcceptsLongNumber() throws Exception {\u000a byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH);\u000a\u000a NonBlockingByteArrayJsonParser p =\u000a (NonBlockingByteArrayJsonParser) factory.createNonBlockingByteArrayParser(ObjectReadContext.empty());\u000a p.feedInput(payload, 0, payload.length);\u000a p.endOfInput();\u000a\u000a boolean foundNumber = false;\u000a try {\u000a while (p.nextToken() != null) {\u000a if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) {\u000a foundNumber = true;\u000a String numberText = p.getText();\u000a assertEquals(TEST_NUMBER_LENGTH, numberText.length(),\u000a \"Async parser silently accepted all \" + TEST_NUMBER_LENGTH + \" digits\");\u000a }\u000a }\u000a // Output to console\u000a System.out.println(\"[ASYNC INT] Accepted number with \" + TEST_NUMBER_LENGTH + \" digits — BUG CONFIRMED\");\u000a assertTrue(foundNumber, \"Parser should have produced a VALUE_NUMBER_INT token\");\u000a } catch (StreamConstraintsException e) {\u000a fail(\"Bug is fixed — async parser now correctly rejects long numbers: \" + e.getMessage());\u000a }\u000a p.close();\u000a }\u000a\u000a private byte[] buildPayloadWithLongInteger(int numDigits) {\u000a StringBuilder sb = new StringBuilder(numDigits + 10);\u000a sb.append(\"{\\\"v\\\":\");\u000a for (int i = 0; i < numDigits; i++) {\u000a sb.append((char) ('1' + (i % 9)));\u000a }\u000a sb.append('}');\u000a return sb.toString().getBytes(StandardCharsets.UTF_8);\u000a }\u000a}\u000a\u000a```\u000a\u000a\u000a### Impact\u000aA malicious actor can send a JSON document with an arbitrarily long number to an application using the async parser (e.g., in a Spring WebFlux or other reactive application). This can cause:\u000a1. **Memory Exhaustion:** Unbounded allocation of memory in the `TextBuffer` to store the number's digits, leading to an `OutOfMemoryError`.\u000a2. **CPU Exhaustion:** If the application subsequently calls `getBigIntegerValue()` or `getDecimalValue()`, the JVM can be tied up in O(n^2) `BigInteger` parsing operations, leading to a CPU-based DoS.\u000a\u000a### Suggested Remediation\u000a\u000aThe async parsing path should be updated to respect the `maxNumberLength` constraint. The simplest fix appears to ensure that `_valueComplete()` or a similar method in the async path calls the appropriate validation methods (`resetInt()` or `resetFloat()`) already present in `ParserBase`, mirroring the behavior of the synchronous parsers.\u000a\u000a**NOTE:** This research was performed in collaboration with [rohan-repos](https://github.com/rohan-repos)\u000a\u000aPackage: com.fasterxml.jackson.core:jackson-core\u000aInstalled Version: 2.15.2\u000aVulnerability GHSA-72hv-8253-57qq\u000aSeverity: MEDIUM\u000aFixed Version: 2.21.1, 2.18.6\u000aLink: [GHSA-72hv-8253-57qq](https://github.com/advisories/GHSA-72hv-8253-57qq)", "type" : "GHSA-72hv-8253-57qq" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "log4j-core-2.25.3.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govway.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" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "log4j-layout-template-json-2.25.3.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govway.war/WEB-INF/lib/log4j-layout-template-json-2.25.3.jar", "fingerprint" : "FALLBACK-78a9f3ba", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "log4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "type" : "CVE-2026-34481" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "spring-security-web-5.8.16.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govway.war/WEB-INF/lib/spring-security-web-5.8.16.jar", "fingerprint" : "FALLBACK-db203dab", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-22732: LanguageSpecificPackageVulnerability\u000a\u000aSpring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22732**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)|\u000a\u000aWhen applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written. \u000aThis issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers:\u000a\u000a: from 5.7.0 through 5.7.21, from 5.8.0 through 5.8.23, from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.8, from 7.0.0 through 7.0.3.\u000a\u000aPackage: org.springframework.security:spring-security-web\u000aInstalled Version: 5.8.16\u000aVulnerability CVE-2026-22732\u000aSeverity: CRITICAL\u000aFixed Version: 6.5.9, 7.0.4\u000aLink: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "spring-security-web-5.8.16.jar(1,0): CVE-2026-22732: : CVE-2026-22732: LanguageSpecificPackageVulnerability\u000a\u000aSpring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22732**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)|\u000a\u000aWhen applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written. \u000aThis issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers:\u000a\u000a: from 5.7.0 through 5.7.21, from 5.8.0 through 5.8.23, from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.8, from 7.0.0 through 7.0.3.\u000a\u000aPackage: org.springframework.security:spring-security-web\u000aInstalled Version: 5.8.16\u000aVulnerability CVE-2026-22732\u000aSeverity: CRITICAL\u000aFixed Version: 6.5.9, 7.0.4\u000aLink: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)", "type" : "CVE-2026-22732" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "commons-lang-2.6.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/commons-lang-2.6.jar", "fingerprint" : "FALLBACK-f48ad3a6", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "type" : "CVE-2025-48924" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "log4j-core-2.25.3.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.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" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "log4j-layout-template-json-2.25.3.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/log4j-layout-template-json-2.25.3.jar", "fingerprint" : "FALLBACK-78a9f3ba", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "log4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "type" : "CVE-2026-34481" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "spring-security-web-5.8.16.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/spring-security-web-5.8.16.jar", "fingerprint" : "FALLBACK-db203dab", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-22732: LanguageSpecificPackageVulnerability\u000a\u000aSpring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22732**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)|\u000a\u000aWhen applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written. \u000aThis issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers:\u000a\u000a: from 5.7.0 through 5.7.21, from 5.8.0 through 5.8.23, from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.8, from 7.0.0 through 7.0.3.\u000a\u000aPackage: org.springframework.security:spring-security-web\u000aInstalled Version: 5.8.16\u000aVulnerability CVE-2026-22732\u000aSeverity: CRITICAL\u000aFixed Version: 6.5.9, 7.0.4\u000aLink: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "spring-security-web-5.8.16.jar(1,0): CVE-2026-22732: : CVE-2026-22732: LanguageSpecificPackageVulnerability\u000a\u000aSpring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22732**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)|\u000a\u000aWhen applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written. \u000aThis issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers:\u000a\u000a: from 5.7.0 through 5.7.21, from 5.8.0 through 5.8.23, from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.8, from 7.0.0 through 7.0.3.\u000a\u000aPackage: org.springframework.security:spring-security-web\u000aInstalled Version: 5.8.16\u000aVulnerability CVE-2026-22732\u000aSeverity: CRITICAL\u000aFixed Version: 6.5.9, 7.0.4\u000aLink: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)", "type" : "CVE-2026-22732" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "struts-core-1.3.10.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/struts-core-1.3.10.jar", "fingerprint" : "FALLBACK-19072676", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "struts-core-1.3.10.jar(1,0): CVE-2023-34396: : CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)", "type" : "CVE-2023-34396" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "commons-lang-2.6.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/commons-lang-2.6.jar", "fingerprint" : "FALLBACK-f48ad3a6", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "type" : "CVE-2025-48924" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "jasperreports-6.20.0.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/jasperreports-6.20.0.jar", "fingerprint" : "FALLBACK-b0f36103", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2025-10492: LanguageSpecificPackageVulnerability\u000a\u000aJasperReports has a Java deserialisation vulnerability\u000a\u000aFor additional help see: **Vulnerability CVE-2025-10492**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|net.sf.jasperreports:jasperreports|7.0.4|[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)|\u000a\u000aA Java deserialisation vulnerability has been discovered in Jaspersoft Library. Improper handling of externally supplied data may allow attackers to execute arbitrary code remotely on systems that use the affected library\u000a\u000aPackage: net.sf.jasperreports:jasperreports\u000aInstalled Version: 6.20.0\u000aVulnerability CVE-2025-10492\u000aSeverity: HIGH\u000aFixed Version: 7.0.4\u000aLink: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "jasperreports-6.20.0.jar(1,0): CVE-2025-10492: : CVE-2025-10492: LanguageSpecificPackageVulnerability\u000a\u000aJasperReports has a Java deserialisation vulnerability\u000a\u000aFor additional help see: **Vulnerability CVE-2025-10492**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|net.sf.jasperreports:jasperreports|7.0.4|[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)|\u000a\u000aA Java deserialisation vulnerability has been discovered in Jaspersoft Library. Improper handling of externally supplied data may allow attackers to execute arbitrary code remotely on systems that use the affected library\u000a\u000aPackage: net.sf.jasperreports:jasperreports\u000aInstalled Version: 6.20.0\u000aVulnerability CVE-2025-10492\u000aSeverity: HIGH\u000aFixed Version: 7.0.4\u000aLink: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)", "type" : "CVE-2025-10492" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "log4j-core-2.25.3.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayAPIMonitor.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" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "log4j-layout-template-json-2.25.3.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/log4j-layout-template-json-2.25.3.jar", "fingerprint" : "FALLBACK-78a9f3ba", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "log4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "type" : "CVE-2026-34481" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "spring-security-web-5.8.16.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/spring-security-web-5.8.16.jar", "fingerprint" : "FALLBACK-db203dab", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-22732: LanguageSpecificPackageVulnerability\u000a\u000aSpring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22732**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)|\u000a\u000aWhen applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written. \u000aThis issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers:\u000a\u000a: from 5.7.0 through 5.7.21, from 5.8.0 through 5.8.23, from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.8, from 7.0.0 through 7.0.3.\u000a\u000aPackage: org.springframework.security:spring-security-web\u000aInstalled Version: 5.8.16\u000aVulnerability CVE-2026-22732\u000aSeverity: CRITICAL\u000aFixed Version: 6.5.9, 7.0.4\u000aLink: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "spring-security-web-5.8.16.jar(1,0): CVE-2026-22732: : CVE-2026-22732: LanguageSpecificPackageVulnerability\u000a\u000aSpring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22732**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)|\u000a\u000aWhen applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written. \u000aThis issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers:\u000a\u000a: from 5.7.0 through 5.7.21, from 5.8.0 through 5.8.23, from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.8, from 7.0.0 through 7.0.3.\u000a\u000aPackage: org.springframework.security:spring-security-web\u000aInstalled Version: 5.8.16\u000aVulnerability CVE-2026-22732\u000aSeverity: CRITICAL\u000aFixed Version: 6.5.9, 7.0.4\u000aLink: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)", "type" : "CVE-2026-22732" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "commons-lang-2.6.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayConsole.war/WEB-INF/lib/commons-lang-2.6.jar", "fingerprint" : "FALLBACK-f48ad3a6", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "type" : "CVE-2025-48924" }, { "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" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "log4j-layout-template-json-2.25.3.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayConsole.war/WEB-INF/lib/log4j-layout-template-json-2.25.3.jar", "fingerprint" : "FALLBACK-78a9f3ba", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "log4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "type" : "CVE-2026-34481" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "struts-core-1.3.10.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayConsole.war/WEB-INF/lib/struts-core-1.3.10.jar", "fingerprint" : "FALLBACK-19072676", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "struts-core-1.3.10.jar(1,0): CVE-2023-34396: : CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)", "type" : "CVE-2023-34396" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "commons-lang-2.6.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/commons-lang-2.6.jar", "fingerprint" : "FALLBACK-f48ad3a6", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)", "type" : "CVE-2025-48924" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "jasperreports-6.20.0.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/jasperreports-6.20.0.jar", "fingerprint" : "FALLBACK-b0f36103", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2025-10492: LanguageSpecificPackageVulnerability\u000a\u000aJasperReports has a Java deserialisation vulnerability\u000a\u000aFor additional help see: **Vulnerability CVE-2025-10492**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|net.sf.jasperreports:jasperreports|7.0.4|[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)|\u000a\u000aA Java deserialisation vulnerability has been discovered in Jaspersoft Library. Improper handling of externally supplied data may allow attackers to execute arbitrary code remotely on systems that use the affected library\u000a\u000aPackage: net.sf.jasperreports:jasperreports\u000aInstalled Version: 6.20.0\u000aVulnerability CVE-2025-10492\u000aSeverity: HIGH\u000aFixed Version: 7.0.4\u000aLink: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "jasperreports-6.20.0.jar(1,0): CVE-2025-10492: : CVE-2025-10492: LanguageSpecificPackageVulnerability\u000a\u000aJasperReports has a Java deserialisation vulnerability\u000a\u000aFor additional help see: **Vulnerability CVE-2025-10492**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|net.sf.jasperreports:jasperreports|7.0.4|[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)|\u000a\u000aA Java deserialisation vulnerability has been discovered in Jaspersoft Library. Improper handling of externally supplied data may allow attackers to execute arbitrary code remotely on systems that use the affected library\u000a\u000aPackage: net.sf.jasperreports:jasperreports\u000aInstalled Version: 6.20.0\u000aVulnerability CVE-2025-10492\u000aSeverity: HIGH\u000aFixed Version: 7.0.4\u000aLink: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)", "type" : "CVE-2025-10492" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "log4j-core-2.25.3.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayMonitor.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" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "log4j-layout-template-json-2.25.3.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/log4j-layout-template-json-2.25.3.jar", "fingerprint" : "FALLBACK-78a9f3ba", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "NORMAL", "toString" : "log4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a * The application uses JsonTemplateLayout.\u000a * The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)", "type" : "CVE-2026-34481" }, { "addedAt" : 0, "authorEmail" : "-", "authorName" : "-", "baseName" : "struts-core-1.3.10.jar", "category" : "", "columnEnd" : 0, "columnStart" : 0, "commit" : "-", "description" : "", "fileName" : "/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/struts-core-1.3.10.jar", "fingerprint" : "FALLBACK-19072676", "lineEnd" : 1, "lineStart" : 1, "message" : "CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)", "moduleName" : "", "origin" : "trivy", "originName" : "Trivy Security Scanner", "packageName" : "-", "reference" : "1398", "severity" : "HIGH", "toString" : "struts-core-1.3.10.jar(1,0): CVE-2023-34396: : CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)", "type" : "CVE-2023-34396" } ], "size" : 53, "toString" : "53 warnings (high: 16, normal: 24, low: 13)" }