0--govway00-/linkitaly/govwayFALLBACK-bc0adcb911CVE-2026-2673: OsPackageVulnerability openssl: OpenSSL TLS 1.3 server may choose unexpected key agreement group For additional help see: **Vulnerability CVE-2026-2673** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)| Issue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected preferred key exchange group when its key exchange group configuration includes the default by using the 'DEFAULT' keyword. Impact summary: A less preferred key exchange may be used even when a more preferred group is supported by both client and server, if the group was not included among the client's initial predicated keyshares. This will sometimes be the case with the new hybrid post-quantum groups, if the client chooses to defer their use until specifically requested by the server. If an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to interpolate the built-in default group list into its own configuration, perhaps adding or removing specific elements, then an implementation defect causes the 'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups were treated as a single sufficiently secure 'tuple', with the server not sending a Hello Retry Request (HRR) even when a group in a more preferred tuple was mutually supported. As a result, the client and server might fail to negotiate a mutually supported post-quantum key agreement group, such as 'X25519MLKEM768', if the client's configuration results in only 'classical' groups (such as 'X25519' being the only ones in the client's initial keyshare prediction). OpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS 1.3 key agreement group on TLS servers. The old syntax had a single 'flat' list of groups, and treated all the supported groups as sufficiently secure. If any of the keyshares predicted by the client were supported by the server the most preferred among these was selected, even if other groups supported by the client, but not included in the list of predicted keyshares would have been more preferred, if included. The new syntax partitions the groups into distinct 'tuples' of roughly equivalent security. Within each tuple the most preferred group included among the client's predicted keyshares is chosen, but if the client supports a group from a more preferred tuple, but did not predict any corresponding keyshares, the server will ask the client to retry the ClientHello (by issuing a Hello Retry Request or HRR) with the most preferred mutually supported group. The above works as expected when the server's configuration uses the built-in default group list, or explicitly defines its own list by directly defining the various desired groups and group 'tuples'. No OpenSSL FIPS modules are affected by this issue, the code in question lies outside the FIPS boundary. OpenSSL 3.6 and 3.5 are vulnerable to this issue. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released. OpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-2673 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-2673: : CVE-2026-2673: OsPackageVulnerability openssl: OpenSSL TLS 1.3 server may choose unexpected key agreement group For additional help see: **Vulnerability CVE-2026-2673** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)| Issue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected preferred key exchange group when its key exchange group configuration includes the default by using the 'DEFAULT' keyword. Impact summary: A less preferred key exchange may be used even when a more preferred group is supported by both client and server, if the group was not included among the client's initial predicated keyshares. This will sometimes be the case with the new hybrid post-quantum groups, if the client chooses to defer their use until specifically requested by the server. If an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to interpolate the built-in default group list into its own configuration, perhaps adding or removing specific elements, then an implementation defect causes the 'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups were treated as a single sufficiently secure 'tuple', with the server not sending a Hello Retry Request (HRR) even when a group in a more preferred tuple was mutually supported. As a result, the client and server might fail to negotiate a mutually supported post-quantum key agreement group, such as 'X25519MLKEM768', if the client's configuration results in only 'classical' groups (such as 'X25519' being the only ones in the client's initial keyshare prediction). OpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS 1.3 key agreement group on TLS servers. The old syntax had a single 'flat' list of groups, and treated all the supported groups as sufficiently secure. If any of the keyshares predicted by the client were supported by the server the most preferred among these was selected, even if other groups supported by the client, but not included in the list of predicted keyshares would have been more preferred, if included. The new syntax partitions the groups into distinct 'tuples' of roughly equivalent security. Within each tuple the most preferred group included among the client's predicted keyshares is chosen, but if the client supports a group from a more preferred tuple, but did not predict any corresponding keyshares, the server will ask the client to retry the ClientHello (by issuing a Hello Retry Request or HRR) with the most preferred mutually supported group. The above works as expected when the server's configuration uses the built-in default group list, or explicitly defines its own list by directly defining the various desired groups and group 'tuples'. No OpenSSL FIPS modules are affected by this issue, the code in question lies outside the FIPS boundary. OpenSSL 3.6 and 3.5 are vulnerable to this issue. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released. OpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-2673 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)CVE-2026-26730--govway00-/linkitaly/govwayFALLBACK-bc0adcb911CVE-2026-2673: OsPackageVulnerability openssl: OpenSSL TLS 1.3 server may choose unexpected key agreement group For additional help see: **Vulnerability CVE-2026-2673** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)| Issue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected preferred key exchange group when its key exchange group configuration includes the default by using the 'DEFAULT' keyword. Impact summary: A less preferred key exchange may be used even when a more preferred group is supported by both client and server, if the group was not included among the client's initial predicated keyshares. This will sometimes be the case with the new hybrid post-quantum groups, if the client chooses to defer their use until specifically requested by the server. If an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to interpolate the built-in default group list into its own configuration, perhaps adding or removing specific elements, then an implementation defect causes the 'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups were treated as a single sufficiently secure 'tuple', with the server not sending a Hello Retry Request (HRR) even when a group in a more preferred tuple was mutually supported. As a result, the client and server might fail to negotiate a mutually supported post-quantum key agreement group, such as 'X25519MLKEM768', if the client's configuration results in only 'classical' groups (such as 'X25519' being the only ones in the client's initial keyshare prediction). OpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS 1.3 key agreement group on TLS servers. The old syntax had a single 'flat' list of groups, and treated all the supported groups as sufficiently secure. If any of the keyshares predicted by the client were supported by the server the most preferred among these was selected, even if other groups supported by the client, but not included in the list of predicted keyshares would have been more preferred, if included. The new syntax partitions the groups into distinct 'tuples' of roughly equivalent security. Within each tuple the most preferred group included among the client's predicted keyshares is chosen, but if the client supports a group from a more preferred tuple, but did not predict any corresponding keyshares, the server will ask the client to retry the ClientHello (by issuing a Hello Retry Request or HRR) with the most preferred mutually supported group. The above works as expected when the server's configuration uses the built-in default group list, or explicitly defines its own list by directly defining the various desired groups and group 'tuples'. No OpenSSL FIPS modules are affected by this issue, the code in question lies outside the FIPS boundary. OpenSSL 3.6 and 3.5 are vulnerable to this issue. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released. OpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-2673 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-2673: : CVE-2026-2673: OsPackageVulnerability openssl: OpenSSL TLS 1.3 server may choose unexpected key agreement group For additional help see: **Vulnerability CVE-2026-2673** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)| Issue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected preferred key exchange group when its key exchange group configuration includes the default by using the 'DEFAULT' keyword. Impact summary: A less preferred key exchange may be used even when a more preferred group is supported by both client and server, if the group was not included among the client's initial predicated keyshares. This will sometimes be the case with the new hybrid post-quantum groups, if the client chooses to defer their use until specifically requested by the server. If an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to interpolate the built-in default group list into its own configuration, perhaps adding or removing specific elements, then an implementation defect causes the 'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups were treated as a single sufficiently secure 'tuple', with the server not sending a Hello Retry Request (HRR) even when a group in a more preferred tuple was mutually supported. As a result, the client and server might fail to negotiate a mutually supported post-quantum key agreement group, such as 'X25519MLKEM768', if the client's configuration results in only 'classical' groups (such as 'X25519' being the only ones in the client's initial keyshare prediction). OpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS 1.3 key agreement group on TLS servers. The old syntax had a single 'flat' list of groups, and treated all the supported groups as sufficiently secure. If any of the keyshares predicted by the client were supported by the server the most preferred among these was selected, even if other groups supported by the client, but not included in the list of predicted keyshares would have been more preferred, if included. The new syntax partitions the groups into distinct 'tuples' of roughly equivalent security. Within each tuple the most preferred group included among the client's predicted keyshares is chosen, but if the client supports a group from a more preferred tuple, but did not predict any corresponding keyshares, the server will ask the client to retry the ClientHello (by issuing a Hello Retry Request or HRR) with the most preferred mutually supported group. The above works as expected when the server's configuration uses the built-in default group list, or explicitly defines its own list by directly defining the various desired groups and group 'tuples'. No OpenSSL FIPS modules are affected by this issue, the code in question lies outside the FIPS boundary. OpenSSL 3.6 and 3.5 are vulnerable to this issue. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released. OpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-2673 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-2673](https://avd.aquasec.com/nvd/cve-2026-2673)CVE-2026-26730--govway00-/linkitaly/govwayFALLBACK-d29a4e2511CVE-2026-28387: OsPackageVulnerability Issue summary: An uncommon configuration of clients performing DANE TL ... For additional help see: **Vulnerability CVE-2026-28387** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)| Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable. The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records. No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28387 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-28387: : CVE-2026-28387: OsPackageVulnerability Issue summary: An uncommon configuration of clients performing DANE TL ... For additional help see: **Vulnerability CVE-2026-28387** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)| Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable. The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records. No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28387 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)CVE-2026-283870--govway00-/linkitaly/govwayFALLBACK-d29a4e2511CVE-2026-28387: OsPackageVulnerability Issue summary: An uncommon configuration of clients performing DANE TL ... For additional help see: **Vulnerability CVE-2026-28387** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)| Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable. The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records. No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28387 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-28387: : CVE-2026-28387: OsPackageVulnerability Issue summary: An uncommon configuration of clients performing DANE TL ... For additional help see: **Vulnerability CVE-2026-28387** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)| Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable. The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records. No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28387 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28387](https://avd.aquasec.com/nvd/cve-2026-28387)CVE-2026-283870--govway00-/linkitaly/govwayFALLBACK-d2b6e71611CVE-2026-28388: OsPackageVulnerability Issue summary: When a delta CRL that contains a Delta CRL Indicator ex ... For additional help see: **Vulnerability CVE-2026-28388** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)| Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application. When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference. Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28388 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-28388: : CVE-2026-28388: OsPackageVulnerability Issue summary: When a delta CRL that contains a Delta CRL Indicator ex ... For additional help see: **Vulnerability CVE-2026-28388** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)| Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application. When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference. Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28388 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)CVE-2026-283880--govway00-/linkitaly/govwayFALLBACK-d2b6e71611CVE-2026-28388: OsPackageVulnerability Issue summary: When a delta CRL that contains a Delta CRL Indicator ex ... For additional help see: **Vulnerability CVE-2026-28388** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)| Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application. When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference. Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28388 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-28388: : CVE-2026-28388: OsPackageVulnerability Issue summary: When a delta CRL that contains a Delta CRL Indicator ex ... For additional help see: **Vulnerability CVE-2026-28388** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)| Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application. When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference. Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28388 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28388](https://avd.aquasec.com/nvd/cve-2026-28388)CVE-2026-283880--govway00-/linkitaly/govwayFALLBACK-d2d3800711CVE-2026-28389: OsPackageVulnerability Issue summary: During processing of a crafted CMS EnvelopedData messag ... For additional help see: **Vulnerability CVE-2026-28389** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)| Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28389 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-28389: : CVE-2026-28389: OsPackageVulnerability Issue summary: During processing of a crafted CMS EnvelopedData messag ... For additional help see: **Vulnerability CVE-2026-28389** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)| Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28389 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)CVE-2026-283890--govway00-/linkitaly/govwayFALLBACK-d2d3800711CVE-2026-28389: OsPackageVulnerability Issue summary: During processing of a crafted CMS EnvelopedData messag ... For additional help see: **Vulnerability CVE-2026-28389** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)| Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28389 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-28389: : CVE-2026-28389: OsPackageVulnerability Issue summary: During processing of a crafted CMS EnvelopedData messag ... For additional help see: **Vulnerability CVE-2026-28389** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)| Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28389 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-28389](https://avd.aquasec.com/nvd/cve-2026-28389)CVE-2026-283890--govway00-/linkitaly/govwayFALLBACK-840d6efb11CVE-2026-28390: OsPackageVulnerability openssl: OpenSSL: Denial of Service due to NULL pointer dereference in CMS EnvelopedData processing For additional help see: **Vulnerability CVE-2026-28390** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|libssl3|3.5.6-r0|[CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)| Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28390 Severity: HIGH Fixed Version: 3.5.6-r0 Link: [CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)trivyTrivy Security Scanner-1398HIGHgovway(1,0): CVE-2026-28390: : CVE-2026-28390: OsPackageVulnerability openssl: OpenSSL: Denial of Service due to NULL pointer dereference in CMS EnvelopedData processing For additional help see: **Vulnerability CVE-2026-28390** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|libssl3|3.5.6-r0|[CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)| Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28390 Severity: HIGH Fixed Version: 3.5.6-r0 Link: [CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)CVE-2026-283900--govway00-/linkitaly/govwayFALLBACK-840d6efb11CVE-2026-28390: OsPackageVulnerability openssl: OpenSSL: Denial of Service due to NULL pointer dereference in CMS EnvelopedData processing For additional help see: **Vulnerability CVE-2026-28390** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|libssl3|3.5.6-r0|[CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)| Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28390 Severity: HIGH Fixed Version: 3.5.6-r0 Link: [CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)trivyTrivy Security Scanner-1398HIGHgovway(1,0): CVE-2026-28390: : CVE-2026-28390: OsPackageVulnerability openssl: OpenSSL: Denial of Service due to NULL pointer dereference in CMS EnvelopedData processing For additional help see: **Vulnerability CVE-2026-28390** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|libssl3|3.5.6-r0|[CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)| Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-28390 Severity: HIGH Fixed Version: 3.5.6-r0 Link: [CVE-2026-28390](https://avd.aquasec.com/nvd/cve-2026-28390)CVE-2026-283900--govway00-/linkitaly/govwayFALLBACK-7e2b053311CVE-2026-31789: OsPackageVulnerability Issue summary: Converting an excessively large OCTET STRING value to a ... For additional help see: **Vulnerability CVE-2026-31789** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)| Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior. If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow. Applications and services that print or log contents of untrusted X.509 certificates are vulnerable to this issue. As the certificates would have to have sizes of over 1 Gigabyte, printing or logging such certificates is a fairly unlikely operation and only 32 bit platforms are affected, this issue was assigned Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-31789 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-31789: : CVE-2026-31789: OsPackageVulnerability Issue summary: Converting an excessively large OCTET STRING value to a ... For additional help see: **Vulnerability CVE-2026-31789** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)| Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior. If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow. Applications and services that print or log contents of untrusted X.509 certificates are vulnerable to this issue. As the certificates would have to have sizes of over 1 Gigabyte, printing or logging such certificates is a fairly unlikely operation and only 32 bit platforms are affected, this issue was assigned Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-31789 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)CVE-2026-317890--govway00-/linkitaly/govwayFALLBACK-7e2b053311CVE-2026-31789: OsPackageVulnerability Issue summary: Converting an excessively large OCTET STRING value to a ... For additional help see: **Vulnerability CVE-2026-31789** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)| Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior. If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow. Applications and services that print or log contents of untrusted X.509 certificates are vulnerable to this issue. As the certificates would have to have sizes of over 1 Gigabyte, printing or logging such certificates is a fairly unlikely operation and only 32 bit platforms are affected, this issue was assigned Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-31789 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-31789: : CVE-2026-31789: OsPackageVulnerability Issue summary: Converting an excessively large OCTET STRING value to a ... For additional help see: **Vulnerability CVE-2026-31789** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |LOW|libssl3|3.5.6-r0|[CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)| Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior. If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow. Applications and services that print or log contents of untrusted X.509 certificates are vulnerable to this issue. As the certificates would have to have sizes of over 1 Gigabyte, printing or logging such certificates is a fairly unlikely operation and only 32 bit platforms are affected, this issue was assigned Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-31789 Severity: LOW Fixed Version: 3.5.6-r0 Link: [CVE-2026-31789](https://avd.aquasec.com/nvd/cve-2026-31789)CVE-2026-317890--govway00-/linkitaly/govwayFALLBACK-5158882411CVE-2026-31790: OsPackageVulnerability openssl: openssl: Information Disclosure from Uninitialized Memory via Invalid RSA Public Key For additional help see: **Vulnerability CVE-2026-31790** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|libssl3|3.5.6-r0|[CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)| Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced. If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext. As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue. The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-31790 Severity: MEDIUM Fixed Version: 3.5.6-r0 Link: [CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)trivyTrivy Security Scanner-1398NORMALgovway(1,0): CVE-2026-31790: : CVE-2026-31790: OsPackageVulnerability openssl: openssl: Information Disclosure from Uninitialized Memory via Invalid RSA Public Key For additional help see: **Vulnerability CVE-2026-31790** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|libssl3|3.5.6-r0|[CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)| Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced. If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext. As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue. The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue. Package: libcrypto3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-31790 Severity: MEDIUM Fixed Version: 3.5.6-r0 Link: [CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)CVE-2026-317900--govway00-/linkitaly/govwayFALLBACK-5158882411CVE-2026-31790: OsPackageVulnerability openssl: openssl: Information Disclosure from Uninitialized Memory via Invalid RSA Public Key For additional help see: **Vulnerability CVE-2026-31790** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|libssl3|3.5.6-r0|[CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)| Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced. If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext. As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue. The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-31790 Severity: MEDIUM Fixed Version: 3.5.6-r0 Link: [CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)trivyTrivy Security Scanner-1398NORMALgovway(1,0): CVE-2026-31790: : CVE-2026-31790: OsPackageVulnerability openssl: openssl: Information Disclosure from Uninitialized Memory via Invalid RSA Public Key For additional help see: **Vulnerability CVE-2026-31790** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|libssl3|3.5.6-r0|[CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)| Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced. If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext. As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue. The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue. Package: libssl3 Installed Version: 3.5.5-r0 Vulnerability CVE-2026-31790 Severity: MEDIUM Fixed Version: 3.5.6-r0 Link: [CVE-2026-31790](https://avd.aquasec.com/nvd/cve-2026-31790)CVE-2026-317900--govway00-/linkitaly/govwayFALLBACK-734c241111CVE-2026-34757: OsPackageVulnerability LIBPNG is a reference library for use in applications that read, creat ... For additional help see: **Vulnerability CVE-2026-34757** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |UNKNOWN|libpng|1.6.57-r0|[CVE-2026-34757](https://avd.aquasec.com/nvd/cve-2026-34757)| LIBPNG 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. Package: libpng Installed Version: 1.6.56-r0 Vulnerability CVE-2026-34757 Severity: UNKNOWN Fixed Version: 1.6.57-r0 Link: [CVE-2026-34757](https://avd.aquasec.com/nvd/cve-2026-34757)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-34757: : CVE-2026-34757: OsPackageVulnerability LIBPNG is a reference library for use in applications that read, creat ... For additional help see: **Vulnerability CVE-2026-34757** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |UNKNOWN|libpng|1.6.57-r0|[CVE-2026-34757](https://avd.aquasec.com/nvd/cve-2026-34757)| LIBPNG 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. Package: libpng Installed Version: 1.6.56-r0 Vulnerability CVE-2026-34757 Severity: UNKNOWN Fixed Version: 1.6.57-r0 Link: [CVE-2026-34757](https://avd.aquasec.com/nvd/cve-2026-34757)CVE-2026-347570--govway00-/linkitaly/govwayFALLBACK-461d9acf11CVE-2026-40200: OsPackageVulnerability An issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based ... For additional help see: **Vulnerability CVE-2026-40200** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |UNKNOWN|musl-utils|1.2.5-r23|[CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)| An 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). Package: musl Installed Version: 1.2.5-r21 Vulnerability CVE-2026-40200 Severity: UNKNOWN Fixed Version: 1.2.5-r23 Link: [CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-40200: : CVE-2026-40200: OsPackageVulnerability An issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based ... For additional help see: **Vulnerability CVE-2026-40200** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |UNKNOWN|musl-utils|1.2.5-r23|[CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)| An 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). Package: musl Installed Version: 1.2.5-r21 Vulnerability CVE-2026-40200 Severity: UNKNOWN Fixed Version: 1.2.5-r23 Link: [CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)CVE-2026-402000--govway00-/linkitaly/govwayFALLBACK-461d9acf11CVE-2026-40200: OsPackageVulnerability An issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based ... For additional help see: **Vulnerability CVE-2026-40200** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |UNKNOWN|musl-utils|1.2.5-r23|[CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)| An 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). Package: musl-utils Installed Version: 1.2.5-r21 Vulnerability CVE-2026-40200 Severity: UNKNOWN Fixed Version: 1.2.5-r23 Link: [CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)trivyTrivy Security Scanner-1398LOWgovway(1,0): CVE-2026-40200: : CVE-2026-40200: OsPackageVulnerability An issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based ... For additional help see: **Vulnerability CVE-2026-40200** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |UNKNOWN|musl-utils|1.2.5-r23|[CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)| An 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). Package: musl-utils Installed Version: 1.2.5-r21 Vulnerability CVE-2026-40200 Severity: UNKNOWN Fixed Version: 1.2.5-r23 Link: [CVE-2026-40200](https://avd.aquasec.com/nvd/cve-2026-40200)CVE-2026-402000--commons-lang-2.6.jar00-/var/govway/batch/generatoreStatistiche/lib/commons-lang-2.6.jarFALLBACK-f48ad3a611CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)trivyTrivy Security Scanner-1398NORMALcommons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)CVE-2025-489240--log4j-core-2.25.3.jar00-/var/govway/batch/generatoreStatistiche/lib/log4j-core-2.25.3.jarFALLBACK-6610c7f611CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)trivyTrivy Security Scanner-1398NORMALlog4j-core-2.25.3.jar(1,0): CVE-2026-34480: : CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)CVE-2026-344800--log4j-layout-template-json-2.25.3.jar00-/var/govway/batch/generatoreStatistiche/lib/log4j-layout-template-json-2.25.3.jarFALLBACK-78a9f3ba11CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)trivyTrivy Security Scanner-1398NORMALlog4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)CVE-2026-344810--catalina.jar00-/usr/local/tomcat/lib/catalina.jarFALLBACK-6a54c21811CVE-2026-24880: LanguageSpecificPackageVulnerability Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response S ... For additional help see: **Vulnerability CVE-2026-24880** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in Apache Tomcat via invalid chunk extension. This 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. Other, unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.20, 10.1.52 or 9.0.116, which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-24880 Severity: HIGH Fixed Version: 9.0.116, 10.1.52, 11.0.20 Link: [CVE-2026-24880](https://avd.aquasec.com/nvd/cve-2026-24880)trivyTrivy Security Scanner-1398HIGHcatalina.jar(1,0): CVE-2026-24880: : CVE-2026-24880: LanguageSpecificPackageVulnerability Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response S ... For additional help see: **Vulnerability CVE-2026-24880** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in Apache Tomcat via invalid chunk extension. This 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. Other, unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.20, 10.1.52 or 9.0.116, which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-24880 Severity: HIGH Fixed Version: 9.0.116, 10.1.52, 11.0.20 Link: [CVE-2026-24880](https://avd.aquasec.com/nvd/cve-2026-24880)CVE-2026-248800--catalina.jar00-/usr/local/tomcat/lib/catalina.jarFALLBACK-82411fbb11CVE-2026-25854: LanguageSpecificPackageVulnerability Occasional URL redirection to untrusted Site ('Open Redirect') vulnera ... For additional help see: **Vulnerability CVE-2026-25854** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Occasional URL redirection to untrusted Site ('Open Redirect') vulnerability in Apache Tomcat via the LoadBalancerDrainingValve. This 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. Other, unsupported versions may also be affected Users are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-25854 Severity: MEDIUM Fixed Version: 9.0.116, 10.1.53, 11.0.20 Link: [CVE-2026-25854](https://avd.aquasec.com/nvd/cve-2026-25854)trivyTrivy Security Scanner-1398NORMALcatalina.jar(1,0): CVE-2026-25854: : CVE-2026-25854: LanguageSpecificPackageVulnerability Occasional URL redirection to untrusted Site ('Open Redirect') vulnera ... For additional help see: **Vulnerability CVE-2026-25854** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Occasional URL redirection to untrusted Site ('Open Redirect') vulnerability in Apache Tomcat via the LoadBalancerDrainingValve. This 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. Other, unsupported versions may also be affected Users are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-25854 Severity: MEDIUM Fixed Version: 9.0.116, 10.1.53, 11.0.20 Link: [CVE-2026-25854](https://avd.aquasec.com/nvd/cve-2026-25854)CVE-2026-258540--catalina.jar00-/usr/local/tomcat/lib/catalina.jarFALLBACK-66a9e9cb11CVE-2026-29129: LanguageSpecificPackageVulnerability Configured cipher preference order not preserved vulnerability in Apac ... For additional help see: **Vulnerability CVE-2026-29129** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Configured cipher preference order not preserved vulnerability in Apache Tomcat. This 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. Users are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-29129 Severity: HIGH Fixed Version: 9.0.116, 10.1.53, 11.0.20 Link: [CVE-2026-29129](https://avd.aquasec.com/nvd/cve-2026-29129)trivyTrivy Security Scanner-1398HIGHcatalina.jar(1,0): CVE-2026-29129: : CVE-2026-29129: LanguageSpecificPackageVulnerability Configured cipher preference order not preserved vulnerability in Apac ... For additional help see: **Vulnerability CVE-2026-29129** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Configured cipher preference order not preserved vulnerability in Apache Tomcat. This 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. Users are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-29129 Severity: HIGH Fixed Version: 9.0.116, 10.1.53, 11.0.20 Link: [CVE-2026-29129](https://avd.aquasec.com/nvd/cve-2026-29129)CVE-2026-291290--catalina.jar00-/usr/local/tomcat/lib/catalina.jarFALLBACK-6d24906511CVE-2026-29145: LanguageSpecificPackageVulnerability CLIENT_CERT authentication does not fail as expected for some scenario ... For additional help see: **Vulnerability CVE-2026-29145** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled vulnerability in Apache Tomcat, Apache Tomcat Native. This 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. Users 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. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-29145 Severity: CRITICAL Fixed Version: 9.0.116, 10.1.53, 11.0.20 Link: [CVE-2026-29145](https://avd.aquasec.com/nvd/cve-2026-29145)trivyTrivy Security Scanner-1398HIGHcatalina.jar(1,0): CVE-2026-29145: : CVE-2026-29145: LanguageSpecificPackageVulnerability CLIENT_CERT authentication does not fail as expected for some scenario ... For additional help see: **Vulnerability CVE-2026-29145** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled vulnerability in Apache Tomcat, Apache Tomcat Native. This 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. Users 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. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-29145 Severity: CRITICAL Fixed Version: 9.0.116, 10.1.53, 11.0.20 Link: [CVE-2026-29145](https://avd.aquasec.com/nvd/cve-2026-29145)CVE-2026-291450--catalina.jar00-/usr/local/tomcat/lib/catalina.jarFALLBACK-6d41295611CVE-2026-29146: LanguageSpecificPackageVulnerability Padding Oracle vulnerability in Apache Tomcat's EncryptInterceptor wit ... For additional help see: **Vulnerability CVE-2026-29146** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Padding Oracle vulnerability in Apache Tomcat's EncryptInterceptor with default configuration. This 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. Users are recommended to upgrade to version 11.0.19, 10.1.53 and 9.0.116, which fixes the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-29146 Severity: HIGH Fixed Version: 9.0.116, 10.1.53, 11.0.19 Link: [CVE-2026-29146](https://avd.aquasec.com/nvd/cve-2026-29146)trivyTrivy Security Scanner-1398HIGHcatalina.jar(1,0): CVE-2026-29146: : CVE-2026-29146: LanguageSpecificPackageVulnerability Padding Oracle vulnerability in Apache Tomcat's EncryptInterceptor wit ... For additional help see: **Vulnerability CVE-2026-29146** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Padding Oracle vulnerability in Apache Tomcat's EncryptInterceptor with default configuration. This 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. Users are recommended to upgrade to version 11.0.19, 10.1.53 and 9.0.116, which fixes the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-29146 Severity: HIGH Fixed Version: 9.0.116, 10.1.53, 11.0.19 Link: [CVE-2026-29146](https://avd.aquasec.com/nvd/cve-2026-29146)CVE-2026-291460--catalina.jar00-/usr/local/tomcat/lib/catalina.jarFALLBACK-f899c98811CVE-2026-32990: LanguageSpecificPackageVulnerability Improper Input Validation vulnerability in Apache Tomcat due to an inc ... For additional help see: **Vulnerability CVE-2026-32990** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Improper Input Validation vulnerability in Apache Tomcat due to an incomplete fix of CVE-2025-66614. This 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. Users are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-32990 Severity: MEDIUM Fixed Version: 9.0.116, 10.1.53, 11.0.20 Link: [CVE-2026-32990](https://avd.aquasec.com/nvd/cve-2026-32990)trivyTrivy Security Scanner-1398NORMALcatalina.jar(1,0): CVE-2026-32990: : CVE-2026-32990: LanguageSpecificPackageVulnerability Improper Input Validation vulnerability in Apache Tomcat due to an inc ... For additional help see: **Vulnerability CVE-2026-32990** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Improper Input Validation vulnerability in Apache Tomcat due to an incomplete fix of CVE-2025-66614. This 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. Users are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-32990 Severity: MEDIUM Fixed Version: 9.0.116, 10.1.53, 11.0.20 Link: [CVE-2026-32990](https://avd.aquasec.com/nvd/cve-2026-32990)CVE-2026-329900--catalina.jar00-/usr/local/tomcat/lib/catalina.jarFALLBACK-ba96c29811CVE-2026-34483: LanguageSpecificPackageVulnerability Improper Encoding or Escaping of Output vulnerability in the JsonAcces ... For additional help see: **Vulnerability CVE-2026-34483** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Improper Encoding or Escaping of Output vulnerability in the JsonAccessLogValve component of Apache Tomcat. This 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. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117 , which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-34483 Severity: HIGH Fixed Version: 9.0.116, 10.1.54, 11.0.21 Link: [CVE-2026-34483](https://avd.aquasec.com/nvd/cve-2026-34483)trivyTrivy Security Scanner-1398HIGHcatalina.jar(1,0): CVE-2026-34483: : CVE-2026-34483: LanguageSpecificPackageVulnerability Improper Encoding or Escaping of Output vulnerability in the JsonAcces ... For additional help see: **Vulnerability CVE-2026-34483** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Improper Encoding or Escaping of Output vulnerability in the JsonAccessLogValve component of Apache Tomcat. This 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. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117 , which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-34483 Severity: HIGH Fixed Version: 9.0.116, 10.1.54, 11.0.21 Link: [CVE-2026-34483](https://avd.aquasec.com/nvd/cve-2026-34483)CVE-2026-344830--catalina.jar00-/usr/local/tomcat/lib/catalina.jarFALLBACK-bb09265c11CVE-2026-34487: LanguageSpecificPackageVulnerability Insertion of Sensitive Information into Log File vulnerability in the ... For additional help see: **Vulnerability CVE-2026-34487** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Insertion of Sensitive Information into Log File vulnerability in the cloud membership for clustering component of Apache Tomcat exposed the Kubernetes bearer token. This 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. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-34487 Severity: HIGH Fixed Version: 9.0.117, 10.1.54, 11.0.21 Link: [CVE-2026-34487](https://avd.aquasec.com/nvd/cve-2026-34487)trivyTrivy Security Scanner-1398HIGHcatalina.jar(1,0): CVE-2026-34487: : CVE-2026-34487: LanguageSpecificPackageVulnerability Insertion of Sensitive Information into Log File vulnerability in the ... For additional help see: **Vulnerability CVE-2026-34487** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Insertion of Sensitive Information into Log File vulnerability in the cloud membership for clustering component of Apache Tomcat exposed the Kubernetes bearer token. This 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. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fix the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-34487 Severity: HIGH Fixed Version: 9.0.117, 10.1.54, 11.0.21 Link: [CVE-2026-34487](https://avd.aquasec.com/nvd/cve-2026-34487)CVE-2026-344870--catalina.jar00-/usr/local/tomcat/lib/catalina.jarFALLBACK-2bda82fb11CVE-2026-34500: LanguageSpecificPackageVulnerability CLIENT_CERT authentication does not fail as expected for some scenario ... For additional help see: **Vulnerability CVE-2026-34500** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled and FFM is used in Apache Tomcat. This 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. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fixes the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-34500 Severity: MEDIUM Fixed Version: 9.0.117, 10.1.54, 11.0.21 Link: [CVE-2026-34500](https://avd.aquasec.com/nvd/cve-2026-34500)trivyTrivy Security Scanner-1398NORMALcatalina.jar(1,0): CVE-2026-34500: : CVE-2026-34500: LanguageSpecificPackageVulnerability CLIENT_CERT authentication does not fail as expected for some scenario ... For additional help see: **Vulnerability CVE-2026-34500** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled and FFM is used in Apache Tomcat. This 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. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fixes the issue. Package: org.apache.tomcat:tomcat-catalina Installed Version: 9.0.115 Vulnerability CVE-2026-34500 Severity: MEDIUM Fixed Version: 9.0.117, 10.1.54, 11.0.21 Link: [CVE-2026-34500](https://avd.aquasec.com/nvd/cve-2026-34500)CVE-2026-345000--commons-lang-2.6.jar00-/usr/local/tomcat/webapps/govway.war/WEB-INF/lib/commons-lang-2.6.jarFALLBACK-f48ad3a611CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)trivyTrivy Security Scanner-1398NORMALcommons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)CVE-2025-489240--hazelcast-5.3.8.jar00-/usr/local/tomcat/webapps/govway.war/WEB-INF/lib/hazelcast-5.3.8.jarFALLBACK-4e8e625711GHSA-72hv-8253-57qq: LanguageSpecificPackageVulnerability jackson-core: Number Length Constraint Bypass in Async Parser Leads to Potential DoS Condition For additional help see: **Vulnerability GHSA-72hv-8253-57qq** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| ### Summary The 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). The standard synchronous parser correctly enforces this limit, but the async parser fails to do so, creating an inconsistent enforcement policy. ### Details The root cause is that the async parsing path in `NonBlockingUtf8JsonParserBase` (and related classes) does not call the methods responsible for number length validation. - The number parsing methods (e.g., `_finishNumberIntegralPart`) accumulate digits into the `TextBuffer` without any length checks. - After parsing, they call `_valueComplete()`, which finalizes the token but does **not** call `resetInt()` or `resetFloat()`. - The `resetInt()`/`resetFloat()` methods in `ParserBase` are where the `validateIntegerLength()` and `validateFPLength()` checks are performed. - Because this validation step is skipped, the `maxNumberLength` constraint is never enforced in the async code path. ### PoC The 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. ```java package tools.jackson.core.unittest.dos; import java.nio.charset.StandardCharsets; import org.junit.jupiter.api.Test; import tools.jackson.core.*; import tools.jackson.core.exc.StreamConstraintsException; import tools.jackson.core.json.JsonFactory; import tools.jackson.core.json.async.NonBlockingByteArrayJsonParser; import static org.junit.jupiter.api.Assertions.*; /** * POC: Number Length Constraint Bypass in Non-Blocking (Async) JSON Parsers * * Authors: sprabhav7, rohan-repos * * maxNumberLength default = 1000 characters (digits). * A number with more than 1000 digits should be rejected by any parser. * * BUG: The async parser never calls resetInt()/resetFloat() which is where * validateIntegerLength()/validateFPLength() lives. Instead it calls * _valueComplete() which skips all number length validation. * * CWE-770: Allocation of Resources Without Limits or Throttling */ class AsyncParserNumberLengthBypassTest { private static final int MAX_NUMBER_LENGTH = 1000; private static final int TEST_NUMBER_LENGTH = 5000; private final JsonFactory factory = new JsonFactory(); // CONTROL: Sync parser correctly rejects a number exceeding maxNumberLength @Test void syncParserRejectsLongNumber() throws Exception { byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH); // Output to console System.out.println("[SYNC] Parsing " + TEST_NUMBER_LENGTH + "-digit number (limit: " + MAX_NUMBER_LENGTH + ")"); try { try (JsonParser p = factory.createParser(ObjectReadContext.empty(), payload)) { while (p.nextToken() != null) { if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) { System.out.println("[SYNC] Accepted number with " + p.getText().length() + " digits — UNEXPECTED"); } } } fail("Sync parser must reject a " + TEST_NUMBER_LENGTH + "-digit number"); } catch (StreamConstraintsException e) { System.out.println("[SYNC] Rejected with StreamConstraintsException: " + e.getMessage()); } } // VULNERABILITY: Async parser accepts the SAME number that sync rejects @Test void asyncParserAcceptsLongNumber() throws Exception { byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH); NonBlockingByteArrayJsonParser p = (NonBlockingByteArrayJsonParser) factory.createNonBlockingByteArrayParser(ObjectReadContext.empty()); p.feedInput(payload, 0, payload.length); p.endOfInput(); boolean foundNumber = false; try { while (p.nextToken() != null) { if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) { foundNumber = true; String numberText = p.getText(); assertEquals(TEST_NUMBER_LENGTH, numberText.length(), "Async parser silently accepted all " + TEST_NUMBER_LENGTH + " digits"); } } // Output to console System.out.println("[ASYNC INT] Accepted number with " + TEST_NUMBER_LENGTH + " digits — BUG CONFIRMED"); assertTrue(foundNumber, "Parser should have produced a VALUE_NUMBER_INT token"); } catch (StreamConstraintsException e) { fail("Bug is fixed — async parser now correctly rejects long numbers: " + e.getMessage()); } p.close(); } private byte[] buildPayloadWithLongInteger(int numDigits) { StringBuilder sb = new StringBuilder(numDigits + 10); sb.append("{\"v\":"); for (int i = 0; i < numDigits; i++) { sb.append((char) ('1' + (i % 9))); } sb.append('}'); return sb.toString().getBytes(StandardCharsets.UTF_8); } } ``` ### Impact A 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: 1. **Memory Exhaustion:** Unbounded allocation of memory in the `TextBuffer` to store the number's digits, leading to an `OutOfMemoryError`. 2. **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. ### Suggested Remediation The 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. **NOTE:** This research was performed in collaboration with [rohan-repos](https://github.com/rohan-repos) Package: com.fasterxml.jackson.core:jackson-core Installed Version: 2.15.2 Vulnerability GHSA-72hv-8253-57qq Severity: MEDIUM Fixed Version: 2.21.1, 2.18.6 Link: [GHSA-72hv-8253-57qq](https://github.com/advisories/GHSA-72hv-8253-57qq)trivyTrivy Security Scanner-1398NORMALhazelcast-5.3.8.jar(1,0): GHSA-72hv-8253-57qq: : GHSA-72hv-8253-57qq: LanguageSpecificPackageVulnerability jackson-core: Number Length Constraint Bypass in Async Parser Leads to Potential DoS Condition For additional help see: **Vulnerability GHSA-72hv-8253-57qq** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| ### Summary The 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). The standard synchronous parser correctly enforces this limit, but the async parser fails to do so, creating an inconsistent enforcement policy. ### Details The root cause is that the async parsing path in `NonBlockingUtf8JsonParserBase` (and related classes) does not call the methods responsible for number length validation. - The number parsing methods (e.g., `_finishNumberIntegralPart`) accumulate digits into the `TextBuffer` without any length checks. - After parsing, they call `_valueComplete()`, which finalizes the token but does **not** call `resetInt()` or `resetFloat()`. - The `resetInt()`/`resetFloat()` methods in `ParserBase` are where the `validateIntegerLength()` and `validateFPLength()` checks are performed. - Because this validation step is skipped, the `maxNumberLength` constraint is never enforced in the async code path. ### PoC The 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. ```java package tools.jackson.core.unittest.dos; import java.nio.charset.StandardCharsets; import org.junit.jupiter.api.Test; import tools.jackson.core.*; import tools.jackson.core.exc.StreamConstraintsException; import tools.jackson.core.json.JsonFactory; import tools.jackson.core.json.async.NonBlockingByteArrayJsonParser; import static org.junit.jupiter.api.Assertions.*; /** * POC: Number Length Constraint Bypass in Non-Blocking (Async) JSON Parsers * * Authors: sprabhav7, rohan-repos * * maxNumberLength default = 1000 characters (digits). * A number with more than 1000 digits should be rejected by any parser. * * BUG: The async parser never calls resetInt()/resetFloat() which is where * validateIntegerLength()/validateFPLength() lives. Instead it calls * _valueComplete() which skips all number length validation. * * CWE-770: Allocation of Resources Without Limits or Throttling */ class AsyncParserNumberLengthBypassTest { private static final int MAX_NUMBER_LENGTH = 1000; private static final int TEST_NUMBER_LENGTH = 5000; private final JsonFactory factory = new JsonFactory(); // CONTROL: Sync parser correctly rejects a number exceeding maxNumberLength @Test void syncParserRejectsLongNumber() throws Exception { byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH); // Output to console System.out.println("[SYNC] Parsing " + TEST_NUMBER_LENGTH + "-digit number (limit: " + MAX_NUMBER_LENGTH + ")"); try { try (JsonParser p = factory.createParser(ObjectReadContext.empty(), payload)) { while (p.nextToken() != null) { if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) { System.out.println("[SYNC] Accepted number with " + p.getText().length() + " digits — UNEXPECTED"); } } } fail("Sync parser must reject a " + TEST_NUMBER_LENGTH + "-digit number"); } catch (StreamConstraintsException e) { System.out.println("[SYNC] Rejected with StreamConstraintsException: " + e.getMessage()); } } // VULNERABILITY: Async parser accepts the SAME number that sync rejects @Test void asyncParserAcceptsLongNumber() throws Exception { byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH); NonBlockingByteArrayJsonParser p = (NonBlockingByteArrayJsonParser) factory.createNonBlockingByteArrayParser(ObjectReadContext.empty()); p.feedInput(payload, 0, payload.length); p.endOfInput(); boolean foundNumber = false; try { while (p.nextToken() != null) { if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) { foundNumber = true; String numberText = p.getText(); assertEquals(TEST_NUMBER_LENGTH, numberText.length(), "Async parser silently accepted all " + TEST_NUMBER_LENGTH + " digits"); } } // Output to console System.out.println("[ASYNC INT] Accepted number with " + TEST_NUMBER_LENGTH + " digits — BUG CONFIRMED"); assertTrue(foundNumber, "Parser should have produced a VALUE_NUMBER_INT token"); } catch (StreamConstraintsException e) { fail("Bug is fixed — async parser now correctly rejects long numbers: " + e.getMessage()); } p.close(); } private byte[] buildPayloadWithLongInteger(int numDigits) { StringBuilder sb = new StringBuilder(numDigits + 10); sb.append("{\"v\":"); for (int i = 0; i < numDigits; i++) { sb.append((char) ('1' + (i % 9))); } sb.append('}'); return sb.toString().getBytes(StandardCharsets.UTF_8); } } ``` ### Impact A 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: 1. **Memory Exhaustion:** Unbounded allocation of memory in the `TextBuffer` to store the number's digits, leading to an `OutOfMemoryError`. 2. **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. ### Suggested Remediation The 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. **NOTE:** This research was performed in collaboration with [rohan-repos](https://github.com/rohan-repos) Package: com.fasterxml.jackson.core:jackson-core Installed Version: 2.15.2 Vulnerability GHSA-72hv-8253-57qq Severity: MEDIUM Fixed Version: 2.21.1, 2.18.6 Link: [GHSA-72hv-8253-57qq](https://github.com/advisories/GHSA-72hv-8253-57qq)GHSA-72hv-8253-57qq0--log4j-core-2.25.3.jar00-/usr/local/tomcat/webapps/govway.war/WEB-INF/lib/log4j-core-2.25.3.jarFALLBACK-6610c7f611CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)trivyTrivy Security Scanner-1398NORMALlog4j-core-2.25.3.jar(1,0): CVE-2026-34480: : CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)CVE-2026-344800--log4j-layout-template-json-2.25.3.jar00-/usr/local/tomcat/webapps/govway.war/WEB-INF/lib/log4j-layout-template-json-2.25.3.jarFALLBACK-78a9f3ba11CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)trivyTrivy Security Scanner-1398NORMALlog4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)CVE-2026-344810--spring-security-web-5.8.16.jar00-/usr/local/tomcat/webapps/govway.war/WEB-INF/lib/spring-security-web-5.8.16.jarFALLBACK-db203dab11CVE-2026-22732: LanguageSpecificPackageVulnerability Spring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers For additional help see: **Vulnerability CVE-2026-22732** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)| When applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written.  This issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers: : 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. Package: org.springframework.security:spring-security-web Installed Version: 5.8.16 Vulnerability CVE-2026-22732 Severity: CRITICAL Fixed Version: 6.5.9, 7.0.4 Link: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)trivyTrivy Security Scanner-1398HIGHspring-security-web-5.8.16.jar(1,0): CVE-2026-22732: : CVE-2026-22732: LanguageSpecificPackageVulnerability Spring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers For additional help see: **Vulnerability CVE-2026-22732** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)| When applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written.  This issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers: : 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. Package: org.springframework.security:spring-security-web Installed Version: 5.8.16 Vulnerability CVE-2026-22732 Severity: CRITICAL Fixed Version: 6.5.9, 7.0.4 Link: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)CVE-2026-227320--commons-lang-2.6.jar00-/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/commons-lang-2.6.jarFALLBACK-f48ad3a611CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)trivyTrivy Security Scanner-1398NORMALcommons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)CVE-2025-489240--log4j-core-2.25.3.jar00-/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/log4j-core-2.25.3.jarFALLBACK-6610c7f611CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)trivyTrivy Security Scanner-1398NORMALlog4j-core-2.25.3.jar(1,0): CVE-2026-34480: : CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)CVE-2026-344800--log4j-layout-template-json-2.25.3.jar00-/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/log4j-layout-template-json-2.25.3.jarFALLBACK-78a9f3ba11CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)trivyTrivy Security Scanner-1398NORMALlog4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)CVE-2026-344810--spring-security-web-5.8.16.jar00-/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/spring-security-web-5.8.16.jarFALLBACK-db203dab11CVE-2026-22732: LanguageSpecificPackageVulnerability Spring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers For additional help see: **Vulnerability CVE-2026-22732** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)| When applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written.  This issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers: : 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. Package: org.springframework.security:spring-security-web Installed Version: 5.8.16 Vulnerability CVE-2026-22732 Severity: CRITICAL Fixed Version: 6.5.9, 7.0.4 Link: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)trivyTrivy Security Scanner-1398HIGHspring-security-web-5.8.16.jar(1,0): CVE-2026-22732: : CVE-2026-22732: LanguageSpecificPackageVulnerability Spring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers For additional help see: **Vulnerability CVE-2026-22732** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)| When applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written.  This issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers: : 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. Package: org.springframework.security:spring-security-web Installed Version: 5.8.16 Vulnerability CVE-2026-22732 Severity: CRITICAL Fixed Version: 6.5.9, 7.0.4 Link: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)CVE-2026-227320--struts-core-1.3.10.jar00-/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/struts-core-1.3.10.jarFALLBACK-1907267611CVE-2023-34396: LanguageSpecificPackageVulnerability Apache Struts vulnerable to memory exhaustion For additional help see: **Vulnerability CVE-2023-34396** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)| Allocation 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. Upgrade to Struts 2.5.31 or 6.1.2.1 or greater Package: org.apache.struts:struts-core Installed Version: 1.3.10 Vulnerability CVE-2023-34396 Severity: HIGH Fixed Version: Link: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)trivyTrivy Security Scanner-1398HIGHstruts-core-1.3.10.jar(1,0): CVE-2023-34396: : CVE-2023-34396: LanguageSpecificPackageVulnerability Apache Struts vulnerable to memory exhaustion For additional help see: **Vulnerability CVE-2023-34396** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)| Allocation 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. Upgrade to Struts 2.5.31 or 6.1.2.1 or greater Package: org.apache.struts:struts-core Installed Version: 1.3.10 Vulnerability CVE-2023-34396 Severity: HIGH Fixed Version: Link: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)CVE-2023-343960--commons-lang-2.6.jar00-/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/commons-lang-2.6.jarFALLBACK-f48ad3a611CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)trivyTrivy Security Scanner-1398NORMALcommons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)CVE-2025-489240--jasperreports-6.20.0.jar00-/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/jasperreports-6.20.0.jarFALLBACK-b0f3610311CVE-2025-10492: LanguageSpecificPackageVulnerability JasperReports has a Java deserialisation vulnerability For additional help see: **Vulnerability CVE-2025-10492** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|net.sf.jasperreports:jasperreports|7.0.4|[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)| A 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 Package: net.sf.jasperreports:jasperreports Installed Version: 6.20.0 Vulnerability CVE-2025-10492 Severity: HIGH Fixed Version: 7.0.4 Link: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)trivyTrivy Security Scanner-1398HIGHjasperreports-6.20.0.jar(1,0): CVE-2025-10492: : CVE-2025-10492: LanguageSpecificPackageVulnerability JasperReports has a Java deserialisation vulnerability For additional help see: **Vulnerability CVE-2025-10492** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|net.sf.jasperreports:jasperreports|7.0.4|[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)| A 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 Package: net.sf.jasperreports:jasperreports Installed Version: 6.20.0 Vulnerability CVE-2025-10492 Severity: HIGH Fixed Version: 7.0.4 Link: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)CVE-2025-104920--log4j-core-2.25.3.jar00-/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/log4j-core-2.25.3.jarFALLBACK-6610c7f611CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)trivyTrivy Security Scanner-1398NORMALlog4j-core-2.25.3.jar(1,0): CVE-2026-34480: : CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)CVE-2026-344800--log4j-layout-template-json-2.25.3.jar00-/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/log4j-layout-template-json-2.25.3.jarFALLBACK-78a9f3ba11CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)trivyTrivy Security Scanner-1398NORMALlog4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)CVE-2026-344810--spring-security-web-5.8.16.jar00-/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/spring-security-web-5.8.16.jarFALLBACK-db203dab11CVE-2026-22732: LanguageSpecificPackageVulnerability Spring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers For additional help see: **Vulnerability CVE-2026-22732** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)| When applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written.  This issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers: : 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. Package: org.springframework.security:spring-security-web Installed Version: 5.8.16 Vulnerability CVE-2026-22732 Severity: CRITICAL Fixed Version: 6.5.9, 7.0.4 Link: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)trivyTrivy Security Scanner-1398HIGHspring-security-web-5.8.16.jar(1,0): CVE-2026-22732: : CVE-2026-22732: LanguageSpecificPackageVulnerability Spring Security: Spring Security: Security policy bypass and information disclosure due to unwritten HTTP headers For additional help see: **Vulnerability CVE-2026-22732** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |CRITICAL|org.springframework.security:spring-security-web|6.5.9, 7.0.4|[CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)| When applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written.  This issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers: : 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. Package: org.springframework.security:spring-security-web Installed Version: 5.8.16 Vulnerability CVE-2026-22732 Severity: CRITICAL Fixed Version: 6.5.9, 7.0.4 Link: [CVE-2026-22732](https://avd.aquasec.com/nvd/cve-2026-22732)CVE-2026-227320--commons-lang-2.6.jar00-/usr/local/tomcat/webapps/govwayConsole.war/WEB-INF/lib/commons-lang-2.6.jarFALLBACK-f48ad3a611CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)trivyTrivy Security Scanner-1398NORMALcommons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)CVE-2025-489240--log4j-core-2.25.3.jar00-/usr/local/tomcat/webapps/govwayConsole.war/WEB-INF/lib/log4j-core-2.25.3.jarFALLBACK-6610c7f611CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)trivyTrivy Security Scanner-1398NORMALlog4j-core-2.25.3.jar(1,0): CVE-2026-34480: : CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)CVE-2026-344800--log4j-layout-template-json-2.25.3.jar00-/usr/local/tomcat/webapps/govwayConsole.war/WEB-INF/lib/log4j-layout-template-json-2.25.3.jarFALLBACK-78a9f3ba11CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)trivyTrivy Security Scanner-1398NORMALlog4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)CVE-2026-344810--struts-core-1.3.10.jar00-/usr/local/tomcat/webapps/govwayConsole.war/WEB-INF/lib/struts-core-1.3.10.jarFALLBACK-1907267611CVE-2023-34396: LanguageSpecificPackageVulnerability Apache Struts vulnerable to memory exhaustion For additional help see: **Vulnerability CVE-2023-34396** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)| Allocation 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. Upgrade to Struts 2.5.31 or 6.1.2.1 or greater Package: org.apache.struts:struts-core Installed Version: 1.3.10 Vulnerability CVE-2023-34396 Severity: HIGH Fixed Version: Link: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)trivyTrivy Security Scanner-1398HIGHstruts-core-1.3.10.jar(1,0): CVE-2023-34396: : CVE-2023-34396: LanguageSpecificPackageVulnerability Apache Struts vulnerable to memory exhaustion For additional help see: **Vulnerability CVE-2023-34396** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)| Allocation 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. Upgrade to Struts 2.5.31 or 6.1.2.1 or greater Package: org.apache.struts:struts-core Installed Version: 1.3.10 Vulnerability CVE-2023-34396 Severity: HIGH Fixed Version: Link: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)CVE-2023-343960--commons-lang-2.6.jar00-/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/commons-lang-2.6.jarFALLBACK-f48ad3a611CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)trivyTrivy Security Scanner-1398NORMALcommons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang For additional help see: **Vulnerability CVE-2025-48924** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)| Uncontrolled Recursion vulnerability in Apache Commons Lang. This 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. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. Package: commons-lang:commons-lang Installed Version: 2.6 Vulnerability CVE-2025-48924 Severity: MEDIUM Fixed Version: Link: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)CVE-2025-489240--jasperreports-6.20.0.jar00-/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/jasperreports-6.20.0.jarFALLBACK-b0f3610311CVE-2025-10492: LanguageSpecificPackageVulnerability JasperReports has a Java deserialisation vulnerability For additional help see: **Vulnerability CVE-2025-10492** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|net.sf.jasperreports:jasperreports|7.0.4|[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)| A 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 Package: net.sf.jasperreports:jasperreports Installed Version: 6.20.0 Vulnerability CVE-2025-10492 Severity: HIGH Fixed Version: 7.0.4 Link: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)trivyTrivy Security Scanner-1398HIGHjasperreports-6.20.0.jar(1,0): CVE-2025-10492: : CVE-2025-10492: LanguageSpecificPackageVulnerability JasperReports has a Java deserialisation vulnerability For additional help see: **Vulnerability CVE-2025-10492** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|net.sf.jasperreports:jasperreports|7.0.4|[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)| A 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 Package: net.sf.jasperreports:jasperreports Installed Version: 6.20.0 Vulnerability CVE-2025-10492 Severity: HIGH Fixed Version: 7.0.4 Link: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)CVE-2025-104920--log4j-core-2.25.3.jar00-/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/log4j-core-2.25.3.jarFALLBACK-6610c7f611CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)trivyTrivy Security Scanner-1398NORMALlog4j-core-2.25.3.jar(1,0): CVE-2026-34480: : CVE-2026-34480: LanguageSpecificPackageVulnerability Apache Log4j Core's XmlLayout fails to sanitize characters For additional help see: **Vulnerability CVE-2026-34480** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4, 3.0.0-beta3|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)| Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output. Package: org.apache.logging.log4j:log4j-core Installed Version: 2.25.3 Vulnerability CVE-2026-34480 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)CVE-2026-344800--log4j-layout-template-json-2.25.3.jar00-/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/log4j-layout-template-json-2.25.3.jarFALLBACK-78a9f3ba11CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)trivyTrivy Security Scanner-1398NORMALlog4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values For additional help see: **Vulnerability CVE-2026-34481** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |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)| Apache 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. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Package: org.apache.logging.log4j:log4j-layout-template-json Installed Version: 2.25.3 Vulnerability CVE-2026-34481 Severity: MEDIUM Fixed Version: 2.25.4, 3.0.0-beta3 Link: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)CVE-2026-344810--struts-core-1.3.10.jar00-/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/struts-core-1.3.10.jarFALLBACK-1907267611CVE-2023-34396: LanguageSpecificPackageVulnerability Apache Struts vulnerable to memory exhaustion For additional help see: **Vulnerability CVE-2023-34396** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)| Allocation 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. Upgrade to Struts 2.5.31 or 6.1.2.1 or greater Package: org.apache.struts:struts-core Installed Version: 1.3.10 Vulnerability CVE-2023-34396 Severity: HIGH Fixed Version: Link: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)trivyTrivy Security Scanner-1398HIGHstruts-core-1.3.10.jar(1,0): CVE-2023-34396: : CVE-2023-34396: LanguageSpecificPackageVulnerability Apache Struts vulnerable to memory exhaustion For additional help see: **Vulnerability CVE-2023-34396** | Severity | Package | Fixed Version | Link | | --- | --- | --- | --- | |HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)| Allocation 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. Upgrade to Struts 2.5.31 or 6.1.2.1 or greater Package: org.apache.struts:struts-core Installed Version: 1.3.10 Vulnerability CVE-2023-34396 Severity: HIGH Fixed Version: Link: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)CVE-2023-343965353 warnings (high: 16, normal: 24, low: 13)