The version of openssl-snapsafe installed on the remote host is prior to 1.0.2k-24. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2OPENSSL-SNAPSAFE-2026-009 advisory.

    Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO     performs short writes can trigger a heap-based out-of-bounds write. (CVE-2025-68160)

    A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union     member is accessed without first validating the type, causing an invalid or NULL pointer dereference when     processing a malformed TimeStamp Response file. (CVE-2025-69420)

    Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the     PKCS12_item_decrypt_d2i_ex() function. (CVE-2025-69421)

    ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function

    NOTE: https://openssl-library.org/news/secadv/20260127.txt (CVE-2026-22796)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of openssl installed on the remote host is prior to 1.0.2k-24. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2026-3168 advisory.

    Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO     performs short writes can trigger a heap-based out-of-bounds write. (CVE-2025-68160)

    A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union     member is accessed without first validating the type, causing an invalid or NULL pointer dereference when     processing a malformed TimeStamp Response file. (CVE-2025-69420)

    Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the     PKCS12_item_decrypt_d2i_ex() function. (CVE-2025-69421)

    ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function

    NOTE: https://openssl-library.org/news/secadv/20260127.txt (CVE-2026-22796)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0346-1 advisory.

    - CVE-2026-22795: Missing ASN1_TYPE validation in PKCS#12 parsing (bsc#1256839).
    - CVE-2025-69420: Missing ASN1_TYPE validation in TS_RESP_verify_response() function (bsc#1256837).
    - CVE-2025-69421: NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function (bsc#1256838).
    - CVE-2026-22796: ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function (bsc#1256840).
    - CVE-2025-68160: Heap out-of-bounds write in BIO_f_linebuffer on short writes (bsc#1256834).
    - CVE-2025-69418: Unauthenticated/unencrypted trailing bytes with low-level OCB function calls     (bsc#1256835).
    - CVE-2025-69419: Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion (bsc#1256836).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0358-1 advisory.

    - CVE-2026-22795: Missing ASN1_TYPE validation in PKCS#12 parsing (bsc#1256839).
    - CVE-2025-69420: Missing ASN1_TYPE validation in TS_RESP_verify_response() function (bsc#1256837).
    - CVE-2025-69421: NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function (bsc#1256838).
    - CVE-2026-22796: ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function (bsc#1256840).
    - CVE-2025-68160: Heap out-of-bounds write in BIO_f_linebuffer on short writes (bsc#1256834).
    - CVE-2025-69418: Unauthenticated/unencrypted trailing bytes with low-level OCB function calls     (bsc#1256835).
    - CVE-2025-69419: Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion (bsc#1256836).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2026:0116 advisory.

 Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

 CVE-2026-22796:
 Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data.

 Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.

 The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.

 Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons the issue was assessed as Low severity.

 The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.

 OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

 CVE-2026-22795:
 Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.

 Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service.

 A type confusion vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid pointer read.

 The location is constrained to a 1-byte address space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF.
 This range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For these reasons, the issue was assessed as Low severity.

 The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.

 OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.

 OpenSSL 1.0.2 is not affected by this issue.

 CVE-2025-69421:
 Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function.

 Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files.

 The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure.

 Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. 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 PKCS#12 implementation is outside the OpenSSL FIPS module boundary.

 OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

 CVE-2025-69420:
 Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.

 Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.

 The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type.
 When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.

 Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.

 The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.

 OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.

 OpenSSL 1.0.2 is not affected by this issue.

 CVE-2025-69419:
 Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.

 Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.

 The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.

 The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer.
 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 PKCS#12 implementation is outside the OpenSSL FIPS module boundary.

 OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.

 OpenSSL 1.0.2 is not affected by this issue.

 CVE-2025-69418:
 Issue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated. Impact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read or tamper with those bytes without detection. The low-level OCB encrypt and decrypt routines in the hardware-accelerated stream path process full 16-byte blocks but do not advance the input/output pointers. The subsequent tail-handling code then operates on the original base pointers, effectively reprocessing the beginning of the buffer while leaving the actual trailing bytes unprocessed. The authentication checksum also excludes the true tail bytes. However, typical OpenSSL consumers using EVP are not affected because the higher-level EVP and provider OCB implementations split inputs so that full blocks and trailing partial blocks are processed in separate calls, avoiding the problematic code path. Additionally, TLS does not use OCB ciphersuites. The vulnerability only affects applications that call the low-level CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with non-block-aligned lengths in a single call on hardware- accelerated builds. For these reasons the issue was assessed as Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as OCB mode is not a FIPS- approved algorithm. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue.

 CVE-2025-68160:
 Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write.

 Impact summary: This out-of-bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application.

 The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write and that write large, newline-free data influenced by an attacker would be affected.
 However, the circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed as 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 BIO implementation is outside the OpenSSL FIPS module boundary.

 OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of OpenSSL installed on the remote host is prior to 3.6.1. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.6.1 advisory.

  - Issue summary: If an application using the SSL_CIPHER_find() function in a QUIC protocol client or server     receives an unknown cipher suite from the peer, a NULL dereference occurs.  Impact summary: A NULL pointer     dereference leads to abnormal termination of the running process causing Denial of Service.  Some     applications call SSL_CIPHER_find() from the client_hello_cb callback on the cipher ID received from the     peer. If this is done with an SSL object implementing the QUIC protocol, NULL pointer dereference will     happen if the examined cipher ID is unknown or unsupported.  As it is not very common to call this     function in applications using the QUIC  protocol and the worst outcome is Denial of Service, the issue     was assessed as Low severity.  The vulnerable code was introduced in the 3.2 version with the addition of     the QUIC protocol support.  The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as     the QUIC implementation is outside the OpenSSL FIPS module boundary.  OpenSSL 3.6, 3.5, 3.4 and 3.3 are     vulnerable to this issue.  OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. Fixed in OpenSSL     3.6.1 (Affected since 3.6.0). (CVE-2025-15468)

  - Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data     where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL     pointer dereference when processing malformed PKCS#7 data.  Impact summary: An application performing     signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can     be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.  The     function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its     type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the     ASN1_TYPE union, causing a crash.  Exploiting this vulnerability requires an attacker to provide a     malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of     Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons     the issue was assessed as Low severity.  The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by     this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.  OpenSSL     3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. Fixed in OpenSSL 3.6.1 (Affected     since 3.6.0). (CVE-2026-22796)

  - Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed     PKCS#12 file.  Impact summary: An application processing a malformed PKCS#12 file can be caused to     dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service.  A type confusion     vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first     validating the type, causing an invalid pointer read.  The location is constrained to a 1-byte address     space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This     range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably     result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or     application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12     files in applications as they are usually used to store private keys which are trusted by definition. For     these reasons, the issue was assessed as Low severity.  The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not     affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.  OpenSSL     3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.  OpenSSL 1.0.2 is not affected by this     issue. Fixed in OpenSSL 3.6.1 (Affected since 3.6.0). (CVE-2026-22795)

  - Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the     PKCS12_item_decrypt_d2i_ex() function.  Impact summary: A NULL pointer dereference can trigger a crash     which leads to Denial of Service for an application processing PKCS#12 files.  The     PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before     dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter     can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to     achieve code execution or memory disclosure.  Exploiting this issue requires an attacker to provide a     malformed PKCS#12 file to an application that processes it. 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 PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
    OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. Fixed in OpenSSL 3.6.1     (Affected since 3.6.0). (CVE-2025-69421)

  - Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an     ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer     dereference when processing a malformed TimeStamp Response file.  Impact summary: An application calling     TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or     NULL pointer when reading, resulting in a Denial of Service.  The functions ossl_ess_get_signing_cert()     and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type.
    When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE     union, causing a crash.  Exploiting this vulnerability requires an attacker to provide a malformed     TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161)     is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue     was assessed as Low severity.  The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,     as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.  OpenSSL 3.6, 3.5,     3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.  OpenSSL 1.0.2 is not affected by this issue. Fixed     in OpenSSL 3.6.1 (Affected since 3.6.0). (CVE-2025-69420)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of OpenSSL installed on the remote host is prior to 3.3.6. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.3.6 advisory.

  - Issue summary: If an application using the SSL_CIPHER_find() function in a QUIC protocol client or server     receives an unknown cipher suite from the peer, a NULL dereference occurs.  Impact summary: A NULL pointer     dereference leads to abnormal termination of the running process causing Denial of Service.  Some     applications call SSL_CIPHER_find() from the client_hello_cb callback on the cipher ID received from the     peer. If this is done with an SSL object implementing the QUIC protocol, NULL pointer dereference will     happen if the examined cipher ID is unknown or unsupported.  As it is not very common to call this     function in applications using the QUIC  protocol and the worst outcome is Denial of Service, the issue     was assessed as Low severity.  The vulnerable code was introduced in the 3.2 version with the addition of     the QUIC protocol support.  The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as     the QUIC implementation is outside the OpenSSL FIPS module boundary.  OpenSSL 3.6, 3.5, 3.4 and 3.3 are     vulnerable to this issue.  OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. Fixed in OpenSSL     3.3.6 (Affected since 3.3.0). (CVE-2025-15468)

  - Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data     where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL     pointer dereference when processing malformed PKCS#7 data.  Impact summary: An application performing     signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can     be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.  The     function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its     type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the     ASN1_TYPE union, causing a crash.  Exploiting this vulnerability requires an attacker to provide a     malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of     Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons     the issue was assessed as Low severity.  The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by     this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.  OpenSSL     3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. Fixed in OpenSSL 3.3.6 (Affected     since 3.3.0). (CVE-2026-22796)

  - Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed     PKCS#12 file.  Impact summary: An application processing a malformed PKCS#12 file can be caused to     dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service.  A type confusion     vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first     validating the type, causing an invalid pointer read.  The location is constrained to a 1-byte address     space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This     range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably     result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or     application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12     files in applications as they are usually used to store private keys which are trusted by definition. For     these reasons, the issue was assessed as Low severity.  The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not     affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.  OpenSSL     3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.  OpenSSL 1.0.2 is not affected by this     issue. Fixed in OpenSSL 3.3.6 (Affected since 3.3.0). (CVE-2026-22795)

  - Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the     PKCS12_item_decrypt_d2i_ex() function.  Impact summary: A NULL pointer dereference can trigger a crash     which leads to Denial of Service for an application processing PKCS#12 files.  The     PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before     dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter     can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to     achieve code execution or memory disclosure.  Exploiting this issue requires an attacker to provide a     malformed PKCS#12 file to an application that processes it. 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 PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
    OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. Fixed in OpenSSL 3.3.6     (Affected since 3.3.0). (CVE-2025-69421)

  - Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an     ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer     dereference when processing a malformed TimeStamp Response file.  Impact summary: An application calling     TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or     NULL pointer when reading, resulting in a Denial of Service.  The functions ossl_ess_get_signing_cert()     and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type.
    When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE     union, causing a crash.  Exploiting this vulnerability requires an attacker to provide a malformed     TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161)     is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue     was assessed as Low severity.  The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,     as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.  OpenSSL 3.6, 3.5,     3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.  OpenSSL 1.0.2 is not affected by this issue. Fixed     in OpenSSL 3.3.6 (Affected since 3.3.0). (CVE-2025-69420)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Debian 12 / 13 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6113 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6113-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     January 27, 2026                      https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : openssl     CVE ID         : CVE-2025-11187 CVE-2025-15467 CVE-2025-15468 CVE-2025-15469                      CVE-2025-66199 CVE-2025-68160 CVE-2025-69418 CVE-2025-69419                      CVE-2025-69420 CVE-2025-69421 CVE-2026-22795 CVE-2026-22796

    Multiple vulnerabilities have been discovered in OpenSSL, a Secure     Sockets Layer toolkit, which may result in denial of service,     information leaks, or potentially remote code execution.

    Additional details can be found in the upstream advisory:
    https://openssl-library.org/news/secadv/20260127.txt

    For the oldstable distribution (bookworm), these problems have been fixed     in version 3.0.18-1~deb12u2.

    For the stable distribution (trixie), these problems have been fixed in     version 3.5.4-1~deb13u2.

    We recommend that you upgrade your openssl packages.

    For the detailed security status of openssl please refer to its security     tracker page at:
    https://security-tracker.debian.org/tracker/openssl

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:1472 advisory.

    OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS)     protocols, as well as a full-strength general-purpose cryptography library.

    Security Fix(es):

    * openssl: OpenSSL: Arbitrary code execution or denial of service through crafted PKCS#12 file     (CVE-2025-11187)

    * openssl: OpenSSL: Remote code execution or Denial of Service via oversized Initialization Vector in CMS     parsing (CVE-2025-15467)

    * openssl: OpenSSL: Denial of Service via NULL pointer dereference in QUIC protocol handling     (CVE-2025-15468)

    * openssl: OpenSSL: Data integrity bypass in `openssl dgst` command due to silent truncation     (CVE-2025-15469)

    * openssl: OpenSSL: Denial of Service due to excessive memory allocation in TLS 1.3 certificate     compression (CVE-2025-66199)

    * openssl: OpenSSL: Denial of Service due to out-of-bounds write in BIO filter (CVE-2025-68160)

    * openssl: OpenSSL: Information disclosure and data tampering via specific low-level OCB     encryption/decryption calls (CVE-2025-69418)

    * openssl: OpenSSL: Arbitrary code execution due to out-of-bounds write in PKCS#12 processing     (CVE-2025-69419)

    * openssl: OpenSSL: Denial of Service via malformed PKCS#12 file processing (CVE-2025-69421)

    * openssl: OpenSSL: Denial of Service via malformed TimeStamp Response (CVE-2025-69420)

    * openssl: OpenSSL: Denial of Service due to type confusion in PKCS#12 file processing (CVE-2026-22795)

    * openssl: OpenSSL: Denial of Service via type confusion in PKCS#7 signature verification (CVE-2026-22796)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0312-1 advisory.

    - CVE-2025-15467: Stack buffer overflow in CMS AuthEnvelopedData parsing (bsc#1256830).
     - CVE-2025-68160: Heap out-of-bounds write in BIO_f_linebuffer on short writes (bsc#1256834).
     - CVE-2025-69418: Unauthenticated/unencrypted trailing bytes with low-level OCB function calls     (bsc#1256835).
     - CVE-2025-69419: Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion (bsc#1256836).
     - CVE-2025-69420: Missing ASN1_TYPE validation in TS_RESP_verify_response() function (bsc#1256837).
     - CVE-2025-69421: NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function (bsc#1256838).
     - CVE-2026-22795: Missing ASN1_TYPE validation in PKCS#12 parsing (bsc#1256839).
     - CVE-2026-22796: ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function (bsc#1256840).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote RockyLinux 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2026:1472 advisory.

    * openssl: OpenSSL: Arbitrary code execution or denial of service through crafted PKCS#12 file     (CVE-2025-11187)

    * openssl: OpenSSL: Remote code execution or Denial of Service via oversized Initialization Vector in CMS     parsing (CVE-2025-15467)

    * openssl: OpenSSL: Denial of Service via NULL pointer dereference in QUIC protocol handling     (CVE-2025-15468)

    * openssl: OpenSSL: Data integrity bypass in `openssl dgst` command due to silent truncation     (CVE-2025-15469)

    * openssl: OpenSSL: Denial of Service due to excessive memory allocation in TLS 1.3 certificate     compression (CVE-2025-66199)

    * openssl: OpenSSL: Denial of Service due to out-of-bounds write in BIO filter (CVE-2025-68160)

    * openssl: OpenSSL: Information disclosure and data tampering via specific low-level OCB     encryption/decryption calls (CVE-2025-69418)

    * openssl: OpenSSL: Arbitrary code execution due to out-of-bounds write in PKCS#12 processing     (CVE-2025-69419)

    * openssl: OpenSSL: Denial of Service via malformed PKCS#12 file processing (CVE-2025-69421)

    * openssl: OpenSSL: Denial of Service via malformed TimeStamp Response (CVE-2025-69420)

    * openssl: OpenSSL: Denial of Service due to type confusion in PKCS#12 file processing (CVE-2026-22795)

    * openssl: OpenSSL: Denial of Service via type confusion in PKCS#7 signature verification (CVE-2026-22796)

Tenable has extracted the preceding description block directly from the RockyLinux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote openSUSE 16 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:20152-1 advisory.

    Security fixes:

     - CVE-2025-11187: Improper validation of PBMAC1 parameters in PKCS#12 MAC verification (bsc#1256829).
     - CVE-2025-15467: Stack buffer overflow in CMS AuthEnvelopedData parsing (bsc#1256830).
     - CVE-2025-15468: NULL dereference in SSL_CIPHER_find() function on unknown cipher ID (bsc#1256831).
     - CVE-2025-15469: openssl dgst one-shot codepath silently truncates inputs >16MB (bsc#1256832).
     - CVE-2025-66199: TLS 1.3 CompressedCertificate excessive memory allocation (bsc#1256833).
     - CVE-2025-68160: Heap out-of-bounds write in BIO_f_linebuffer on short writes (bsc#1256834).
     - CVE-2025-69418: Unauthenticated/unencrypted trailing bytes with low-level OCB function calls     (bsc#1256835).
     - CVE-2025-69419: Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion (bsc#1256836).
     - CVE-2025-69420: Missing ASN1_TYPE validation in TS_RESP_verify_response() function (bsc#1256837).
     - CVE-2025-69421: NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function (bsc#1256838).
     - CVE-2026-22795: Missing ASN1_TYPE validation in PKCS#12 parsing (bsc#1256839).
     - CVE-2026-22796: ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function (bsc#1256840).

    Other fixes:

    - Enable livepatching support for ppc64le (bsc#1257274).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
299547	Amazon Linux 2 : openssl-snapsafe, --advisory ALAS2OPENSSL-SNAPSAFE-2026-009 (ALASOPENSSL-SNAPSAFE-2026-009)	Nessus	Amazon Linux Local Security Checks	2026/2/19	2026/2/19	high
299556	Amazon Linux 2 : openssl, --advisory ALAS2-2026-3168 (ALAS-2026-3168)	Nessus	Amazon Linux Local Security Checks	2026/2/19	2026/4/30	high
297432	SUSE SLES15 / openSUSE 15 Security Update : openssl-1_1 (SUSE-SU-2026:0346-1)	Nessus	SuSE Local Security Checks	2026/1/31	2026/2/3	high
297613	SUSE SLES12 Security Update : openssl-1_1 (SUSE-SU-2026:0358-1)	Nessus	SuSE Local Security Checks	2026/2/3	2026/2/3	high
300921	TencentOS Server 4: edk2 (TSSA-2026:0116)	Nessus	Tencent Local Security Checks	2026/3/5	2026/3/5	high
296770	OpenSSL 3.6.0 < 3.6.1 Multiple Vulnerabilities	Nessus	Web Servers	2026/1/27	2026/4/30	high
296784	OpenSSL 3.3.0 < 3.3.6 Multiple Vulnerabilities	Nessus	Web Servers	2026/1/27	2026/4/30	high
296910	Debian dsa-6113 : libcrypto3-udeb - security update	Nessus	Debian Local Security Checks	2026/1/27	2026/2/3	high
297044	RHEL 10 : openssl (RHSA-2026:1472)	Nessus	Red Hat Local Security Checks	2026/1/28	2026/4/30	high
297086	SUSE SLES15 / openSUSE 15 Security Update : openssl-3 (SUSE-SU-2026:0312-1)	Nessus	SuSE Local Security Checks	2026/1/29	2026/4/30	high
297284	RockyLinux 10 : openssl (RLSA-2026:1472)	Nessus	Rocky Linux Local Security Checks	2026/1/31	2026/2/3	high
297791	openSUSE 16 Security Update : openssl-3 (openSUSE-SU-2026:20152-1)	Nessus	SuSE Local Security Checks	2026/2/4	2026/2/4	high

检测

插件搜索

high

high

high

high

high

high

high

high

high

high

high

high