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.

redhat RHSA-2026:1473: RHSA-2026:1473: openssl security update (Important)

freebsd 4b824428-fb93-11f0-b194-8447094a420f: OpenSSL -- Multiple vulnerabilities

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 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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Debian Linux - openssl - None  Red Hat Enterprise Linux - openssl: OpenSSL: Denial of Service due to out-     of-bounds write in BIO filter (CVE-2025-68160)

Note that Nessus relies on the presence of the package as reported by the vendor.

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 1.1.1ze. It is, therefore, affected by multiple vulnerabilities as referenced in the 1.1.1ze advisory.

  - 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 1.1.1ze (Affected since 1.1.1). (CVE-2026-22795)

  - 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 1.1.1ze (Affected     since 1.1.1). (CVE-2026-22796)

  - 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 1.1.1ze     (Affected since 1.1.1). (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 1.1.1ze (Affected since 1.1.1). (CVE-2025-69420)

  - 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. Fixed in     OpenSSL 1.1.1ze (Affected since 1.1.1). (CVE-2025-69419)

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.5.5. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.5.5 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.5.5 (Affected since 3.5.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.5.5 (Affected     since 3.5.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.5.5 (Affected since 3.5.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.5.5     (Affected since 3.5.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.5.5 (Affected since 3.5.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 1.0.2zn. It is, therefore, affected by multiple vulnerabilities as referenced in the 1.0.2zn advisory.

  - 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 1.0.2zn (Affected     since 1.0.2). (CVE-2026-22796)

  - 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 1.0.2zn     (Affected since 1.0.2). (CVE-2025-69421)

  - 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. Fixed in OpenSSL 1.0.2zn (Affected since 1.0.2). (CVE-2025-68160)

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.4.4. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.4.4 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.4.4 (Affected since 3.4.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.4.4 (Affected     since 3.4.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.4.4 (Affected since 3.4.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.4.4     (Affected since 3.4.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.4.4 (Affected since 3.4.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.0.19. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.0.19 advisory.

  - 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.0.19 (Affected     since 3.0.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.0.19 (Affected since 3.0.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.0.19     (Affected since 3.0.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.0.19 (Affected since 3.0.0). (CVE-2025-69420)

  - 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. Fixed in     OpenSSL 3.0.19 (Affected since 3.0.0). (CVE-2025-69419)

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

ID	Name	Product	Family	Severity
296910	Debian dsa-6113 : libcrypto3-udeb - security update	Nessus	Debian Local Security Checks	medium
296784	OpenSSL 3.3.0 < 3.3.6 Multiple Vulnerabilities	Nessus	Web Servers	high
296782	Linux Distros Unpatched Vulnerability : CVE-2025-68160	Nessus	Misc.	high
296770	OpenSSL 3.6.0 < 3.6.1 Multiple Vulnerabilities	Nessus	Web Servers	high
296769	OpenSSL 1.1.1 < 1.1.1ze Multiple Vulnerabilities	Nessus	Web Servers	medium
296768	OpenSSL 3.5.0 < 3.5.5 Multiple Vulnerabilities	Nessus	Web Servers	high
296767	OpenSSL 1.0.2 < 1.0.2zn Multiple Vulnerabilities	Nessus	Web Servers	high
296766	OpenSSL 3.4.0 < 3.4.4 Multiple Vulnerabilities	Nessus	Web Servers	high
296765	OpenSSL 3.0.0 < 3.0.19 Multiple Vulnerabilities	Nessus	Web Servers	high

Detections

Analytics

CVE-2025-68160

high

Tenable Plugins

Coming Soon

medium

high

high

high

medium

high

high

high

high