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

  - Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference     during CMS decryption. Impact summary: This NULL pointer dereference leads to an application crash and a     Denial of Service. The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in     the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based     CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it     was present. An attacker who supplies such a CMS message to an application performing password-based CMS     decryption can trigger an application crash, leading to a Denial of Service. Applications that process     password-encrypted CMS messages may be affected. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not     affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary. (CVE-2026-42766)

  - Issue summary: A signed integer overflow when sizing the destination buffer for Unicode output in     ASN1_mbstring_ncopy() can lead to a heap buffer overflow. Impact summary: A heap buffer overflow may lead     to a crash or possibly attacker controlled code execution or other undefined behaviour. In     ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination size for Unicode output is computed in a     signed int: by left shift of the input character count for BMPSTRING (UTF-16) and UNIVERSALSTRING     (UTF-32), and by summing per-character byte counts for UTF8STRING. The calculation overflows when the     input reaches around 2^30 characters. In the worst case (UNIVERSALSTRING at 2^30 characters) the size     wraps to zero, OPENSSL_malloc(1) is called, and the subsequent character copy writes several gigabytes     past the one-byte allocation. X.509 certificate processing routes through ASN1_STRING_set_by_NID(), whose     DIRSTRING_TYPE mask excludes UNIVERSALSTRING and whose per-NID size limits cap the input length; no     network protocol or certificate-handling path in OpenSSL exercises the overflow. Triggering the bug     requires an application that calls ASN1_mbstring_copy() or ASN1_mbstring_ncopy() directly, or registers a     custom string type via ASN1_STRING_TABLE_add(), with attacker-controlled input on the order of half a     gigabyte or more. For these reasons this issue was assigned Low severity. The FIPS modules in 4.0, 3.6,     3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module     boundary. (CVE-2026-7383)

  - Issue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied     CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in     kek_unwrap_key(). Impact summary: A heap buffer over-read may trigger a crash which leads to Denial of     Service for an application if the input buffer ends at a memory page boundary and the following page is     unmapped. There is no information disclosure as the over-read bytes are not revealed to the attacker. The     key unwrapping function performs a check-byte test as specified in the RFC that reads 7 bytes from a heap     allocation that is based on the wrapped key length from the message. There is a minimum length check based     on the block length of the wrapping cipher. However the cipher is selected from an OID carried in the     attacker's PWRI keyEncryptionAlgorithm with no requirement that the cipher be a block cipher. When an     attacker selects a stream-mode cipher the guard will be ineffective and the allocated buffer containing     the unwrapped key can be too small to fit the check-bytes specified in the RFC and a buffer over-read can     happen. Applications calling CMS_decrypt() or CMS_decrypt_set1_password() (equivalently openssl cms
    -decrypt -pwri_password ...) on untrusted CMS data are vulnerable to this issue. No password knowledge is     required: the over-read happens during the unwrap attempt before any authentication succeeds. The over-     read is limited to a few bytes and is not written to output, so there is no information disclosure.
    Triggering a crash requires the allocation to border unmapped memory, which is unlikely with the normal     allocator. The FIPS modules are not affected by this issue. (CVE-2026-9076)

  - Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during     PKCS#7 signature verification. Impact summary: A use-after-free may result in process crashes, heap     corruption, or potentially remote code execution. When processing a PKCS#7 or S/MIME signed message, if     the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a     caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in     a use-after-free condition. In the common case this occurs when the application later calls BIO_free() on     the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO     usage patterns, this may result in a crash or other memory corruption. In some application contexts this     may potentially be exploitable for remote code execution. Applications that process PKCS#7 or S/MIME     signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this     processing are not affected. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this     issue, as the affected code is outside the OpenSSL FIPS module boundary. (CVE-2026-45447)

  - Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive element whose content     exceeds 2 gigabytes in length may cause a heap buffer over-read on 64-bit Unix and Unix-like platforms.
    Impact summary: The heap buffer over-read may crash the application (Denial of Service) or to load into     the decoded ASN.1 object contents of memory beyond the end of the input buffer. More typically such ASN.1     elements would instead be truncated. An integer truncation in OpenSSL's ASN.1 decoder causes the content     length of an ASN.1 primitive element to be mishandled when it exceeds 2 gigabytes. In the worst case the     truncated length is treated as a request to scan the binary content for a terminating zero byte, possibly     causing OpenSSL to read either less than or beyond the end of the allocated buffer. Applications that pass     attacker-supplied data to d2i_X509(), d2i_PKCS7(), or any other d2i_* decoding function are affected.
    OpenSSL's own command-line tools are not vulnerable, as data read through the BIO layer is checked before     it reaches the affected code. The issue only affects 64-bit Unix and Unix-like platforms; 32-bit platforms     and 64-bit Windows are not affected. The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by     this issue, as the affected code is outside the OpenSSL FIPS module boundary. (CVE-2026-34180)

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

Detections

Analytics

OpenSSL 1.0.2 < 1.0.2zq Multiple Vulnerabilities

critical Nessus Plugin ID 320141

Version 1.2

Version 1.1

Version 1.2 Jun 10, 2026, 6:51 AM CVSS metrics ("CVSSv3 score" set to 9.8) CVSS metrics ("CVSSv3 vector" set to "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H") CVSSv3 score source (changed from "CVE-2026-7383" to "CVE-2026-45447") Plugin Feed: 202606100651
Version 1.1 Jun 10, 2026, 12:51 AM New Plugin Feed: 202606100051