Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot interface, the application-supplied initialisation vector (IV) is silently discarded. Impact summary: Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to compute the authentication tag, the tag depends only on the (key, IV) pair and not on the plaintext or ciphertext, allowing universal forgery of arbitrary ciphertext from a single captured message. OpenSSL provides two ways to drive a cipher: the documented streaming interface (EVP_CipherUpdate / EVP_CipherFinal_ex) and a lower-level one-shot, EVP_Cipher(), whose documentation explicitly recommends against use by applications in favour of EVP_CipherUpdate() and EVP_CipherFinal_ex(). The OCB provider's streaming handler flushes the application-supplied IV into the OCB context before processing data; the one-shot handler did not. Every call to EVP_Cipher() on an AES-OCB context therefore ran with the all-zero key-derived offset state left by cipher initialisation, regardless of the caller's IV. If EVP_EncryptFinal_ex() is subsequently used to obtain the authentication tag, the deferred IV setup runs at that point and clears the running checksum that should have been accumulated over the plaintext. The resulting tag is a function of (key, IV) only and verifies against any ciphertext produced under the same (key, IV) pair. The OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a TLS cipher suite, and libssl does not call EVP_Cipher() in any case. Applications that drive AES-OCB through the documented streaming AEAD API (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected. Only applications that combine the AES-OCB cipher with the EVP_Cipher() one-shot API are vulnerable. The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as AES-OCB is outside the OpenSSL FIPS module boundary.

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

    This update for openssl-3 fixes the following issues

    - CVE-2026-7383: Possible Heap Buffer Overflow in ASN.1 Multibyte String Conversion (bsc#1266340).
    - CVE-2026-9076: Out-of-Bounds Read in CMS Password-Based Decryption (bsc#1266341).
    - CVE-2026-34180: Heap Buffer Over-read in ASN.1 Content Parsing (bsc#1266342).
    - CVE-2026-42766: Possible NULL Dereference in Password-Based CMS Decryption (bsc#1266349).
    - CVE-2026-42770: FFC-DH Peer Validation Uses Attacker-Supplied q (bsc#1266353).
    - CVE-2026-45445: AES-OCB IV Ignored on EVP_Cipher() Path (bsc#1266355).
    - CVE-2026-45446: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes     (bsc#1266356).
    - CVE-2026-45447: Heap Use-After-Free in OpenSSL PKCS7_verify() (bsc#1266357).

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 SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:2393-1 advisory.

    This update for openssl-3 fixes the following issues

    - CVE-2026-7383: Possible Heap Buffer Overflow in ASN.1 Multibyte String Conversion (bsc#1266340).
    - CVE-2026-9076: Out-of-Bounds Read in CMS Password-Based Decryption (bsc#1266341).
    - CVE-2026-34180: Heap Buffer Over-read in ASN.1 Content Parsing (bsc#1266342).
    - CVE-2026-34182: CMS AuthEnvelopedData Processing May Accept Forged Messages (bsc#1266344).
    - CVE-2026-42766: Possible NULL Dereference in Password-Based CMS Decryption (bsc#1266349).
    - CVE-2026-42770: FFC-DH Peer Validation Uses Attacker-Supplied q (bsc#1266353).
    - CVE-2026-45445: AES-OCB IV Ignored on EVP_Cipher() Path (bsc#1266355).
    - CVE-2026-45446: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes     (bsc#1266356).
    - CVE-2026-45447: Heap Use-After-Free in OpenSSL PKCS7_verify() (bsc#1266357).

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.

An update of the openssl package has been released.

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

    * openssl: OpenSSL: Heap buffer overflow due to signed integer overflow in Unicode output sizing     (CVE-2026-7383)

    * openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption     (CVE-2026-9076)

    * openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information     disclosure. (CVE-2026-34180)

    * openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys (CVE-2026-34181)

    * openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages (CVE-2026-34182)

    * openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler (CVE-2026-34183)

    * openssl: NULL pointer dereference in QUIC server initial packet handling (CVE-2026-42764)

    * openssl: Possible NULL Dereference in Password-Based CMS Decryption (CVE-2026-42766)

    * openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption (CVE-2026-42767)

    * openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() (CVE-2026-42768)

    * openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate (CVE-2026-42769)

    * openssl: FFC-DH Peer Validation Uses Attacker-Supplied q (CVE-2026-42770)

    * openssl: AES-OCB IV Ignored on EVP_Cipher() Path (CVE-2026-45445)

    * openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes (CVE-2026-45446)

    * openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() (CVE-2026-45447)

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 RockyLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2026:25239 advisory.

    * openssl: OpenSSL: Heap buffer overflow due to signed integer overflow in Unicode output sizing     (CVE-2026-7383)

    * openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption     (CVE-2026-9076)

    * openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information     disclosure. (CVE-2026-34180)

    * openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys (CVE-2026-34181)

    * openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages (CVE-2026-34182)

    * openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler (CVE-2026-34183)

    * openssl: NULL pointer dereference in QUIC server initial packet handling (CVE-2026-42764)

    * openssl: Possible NULL Dereference in Password-Based CMS Decryption (CVE-2026-42766)

    * openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption (CVE-2026-42767)

    * openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() (CVE-2026-42768)

    * openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate (CVE-2026-42769)

    * openssl: FFC-DH Peer Validation Uses Attacker-Supplied q (CVE-2026-42770)

    * openssl: AES-OCB IV Ignored on EVP_Cipher() Path (CVE-2026-45445)

    * openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes (CVE-2026-45446)

    * openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() (CVE-2026-45447)

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 Fedora 44 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-228373a496 advisory.

    Rebase to OpenSSL 3.5.7     Fixes CVE-2026-45447     Fixes CVE-2026-34182     Fixes CVE-2026-34183     Fixes CVE-2026-42764     Fixes CVE-2026-45445     Fixes CVE-2026-7383     Fixes CVE-2026-9076     Fixes CVE-2026-34180     Fixes CVE-2026-34181     Fixes CVE-2026-42766     Fixes CVE-2026-42767     Fixes CVE-2026-42768     Fixes CVE-2026-42769     Fixes CVE-2026-42770     Fixes CVE-2026-45446

Tenable has extracted the preceding description block directly from the Fedora 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 AlmaLinux 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2026:25237 advisory.

    * openssl: OpenSSL: Heap buffer overflow due to signed integer overflow in Unicode output sizing     (CVE-2026-7383)
      * openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption     (CVE-2026-9076)
      * openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information     disclosure. (CVE-2026-34180)
      * openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys (CVE-2026-34181)
      * openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages (CVE-2026-34182)
      * openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler (CVE-2026-34183)
      * openssl: NULL pointer dereference in QUIC server initial packet handling (CVE-2026-42764)
      * openssl: Possible NULL Dereference in Password-Based CMS Decryption (CVE-2026-42766)
      * openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption (CVE-2026-42767)
      * openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt()     (CVE-2026-42768)
      * openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate (CVE-2026-42769)
      * openssl: FFC-DH Peer Validation Uses Attacker-Supplied q (CVE-2026-42770)
      * openssl: AES-OCB IV Ignored on EVP_Cipher() Path (CVE-2026-45445)
      * openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes (CVE-2026-45446)
      * openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() (CVE-2026-45447)

Tenable has extracted the preceding description block directly from the AlmaLinux 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 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:25239 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: Heap buffer overflow due to signed integer overflow in Unicode output sizing     (CVE-2026-7383)

    * openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption     (CVE-2026-9076)

    * openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information     disclosure. (CVE-2026-34180)

    * openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys (CVE-2026-34181)

    * openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages (CVE-2026-34182)

    * openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler (CVE-2026-34183)

    * openssl: NULL pointer dereference in QUIC server initial packet handling (CVE-2026-42764)

    * openssl: Possible NULL Dereference in Password-Based CMS Decryption (CVE-2026-42766)

    * openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption (CVE-2026-42767)

    * openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() (CVE-2026-42768)

    * openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate (CVE-2026-42769)

    * openssl: FFC-DH Peer Validation Uses Attacker-Supplied q (CVE-2026-42770)

    * openssl: AES-OCB IV Ignored on EVP_Cipher() Path (CVE-2026-45445)

    * openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes (CVE-2026-45446)

    * openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() (CVE-2026-45447)

    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 Redhat Enterprise Linux 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:25237 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: Heap buffer overflow due to signed integer overflow in Unicode output sizing     (CVE-2026-7383)

    * openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption     (CVE-2026-9076)

    * openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information     disclosure. (CVE-2026-34180)

    * openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys (CVE-2026-34181)

    * openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages (CVE-2026-34182)

    * openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler (CVE-2026-34183)

    * openssl: NULL pointer dereference in QUIC server initial packet handling (CVE-2026-42764)

    * openssl: Possible NULL Dereference in Password-Based CMS Decryption (CVE-2026-42766)

    * openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption (CVE-2026-42767)

    * openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() (CVE-2026-42768)

    * openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate (CVE-2026-42769)

    * openssl: FFC-DH Peer Validation Uses Attacker-Supplied q (CVE-2026-42770)

    * openssl: AES-OCB IV Ignored on EVP_Cipher() Path (CVE-2026-45445)

    * openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes (CVE-2026-45446)

    * openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() (CVE-2026-45447)

    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 version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 259b562f-64ab-11f1-8607-8447094a420f advisory.

    The OpenSSL project reports:
    Eighteen vulnerabilities in OpenSSL library.
                Highest classification High.

Tenable has extracted the preceding description block directly from the FreeBSD 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 FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the a57fe2c1-6476-11f1-958d-bc241121aa0a advisory.

    Multiple issues have been reported as part of this advisory               with different issues affecting different OpenSSL versions and               therefore different FreeBSD versions.  Instead of exhaustively               listing detailed writeups for each issue, please see the referenced               advisory from OpenSSL.
    Issues affecting FreeBSD 15.x (OpenSSL 3.5):
    Issues affecting FreeBSD 14.x (OpenSSL 3.0):
    The issues include heap buffer overflows and over-reads, NULL               pointer dereferences, a use-after-free, unbounded memory allocation,               and several cryptographic flaws permitting message forgery, integrity               bypass, or recovery of a private key.
    Security impact ranges from a Denial of Service to a potential               remote code execution.  See the OpenSSL advisory for specific               details.

Tenable has extracted the preceding description block directly from the FreeBSD 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 Ubuntu 22.04 LTS / 24.04 LTS / 25.10 / 26.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-8414-1 advisory.

    Frank Buss discovered that OpenSSL had a heap buffer over-read in ASN.1 content parsing. An attacker could     possibly use this issue to cause OpenSSL to crash, resulting in a denial of service, or obtain sensitive     information. (CVE-2026-34180)

    Pavol Zacik and Alex Gaynor discovered that OpenSSL incorrectly accepted PKCS#12 files with short HMAC     keys when using PBMAC1. An attacker could possibly use this issue to bypass integrity checks. This issue     only affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-34181)

    Asim Viladi Oglu Manizada and Alex Gaynor discovered that OpenSSL could accept forged CMS     AuthEnvelopedData messages. An attacker could possibly use this issue to bypass message authentication     checks. (CVE-2026-34182)

    Abhinav Agarwal discovered that OpenSSL had unbounded memory growth in the QUIC PATH_CHALLENGE handler. A     remote attacker could possibly use this issue to cause OpenSSL to use excessive resources, leading to a     denial of service. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-34183)

    Sunwoo Lee, Hyuk Lim, and Seunghyun Yoon discovered that OpenSSL had a NULL pointer dereference in QUIC     server initial packet handling. A remote attacker could possibly use this issue to cause OpenSSL to crash,     resulting in a denial of service. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS.
    (CVE-2026-42764)

    Mayank Jangid, Kushal Khemka, Hari Priandana, Bhabani Sankar Das, and Qifan Zhang discovered that OpenSSL     had a possible NULL dereference in password- based CMS decryption. An attacker could possibly use this     issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-42766)

    Zhanpeng Liu, Guannan Wang, and Guancheng Li discovered that OpenSSL had a NULL pointer dereference in     CRMF EncryptedValue decryption. An attacker could possibly use this issue to cause OpenSSL to crash,     resulting in a denial of service. (CVE-2026-42767)

    Alex Gaynor discovered that OpenSSL had a Bleichenbacher oracle in CMS_decrypt() and PKCS7_decrypt() with     multiple RecipientInfo values. An attacker could possibly use this issue to obtain sensitive information.
    This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-42768)

    Alex Gaynor discovered that OpenSSL had a trust-anchor substitution issue in CMP rootCaKeyUpdate     processing. An attacker could possibly use this issue to bypass certificate trust validation. This issue     only affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-42769)

    Alex Gaynor discovered that OpenSSL used attacker-supplied parameters when validating FFC-DH peers. An     attacker could possibly use this issue to weaken key validation and compromise security guarantees.
    (CVE-2026-42770)

    Alex Gaynor discovered that OpenSSL could ignore the IV in AES-OCB mode on the EVP_Cipher() path. An     attacker could possibly use this issue to bypass cryptographic protections and obtain sensitive     information. (CVE-2026-45445)

    Alex Gaynor discovered that OpenSSL had incorrect tag processing for empty messages in AES-GCM-SIV and     AES-SIV modes. An attacker could possibly use this issue to bypass cryptographic integrity checks.
    (CVE-2026-45446)

    Thai Duong discovered that OpenSSL had a heap use-after-free in PKCS7_verify(). An attacker could possibly     use this issue to cause OpenSSL to crash, resulting in a denial of service, or execute arbitrary code.
    (CVE-2026-45447)

    Zehua Qiao and Jinwen He discovered that OpenSSL had a possible heap buffer overflow in ASN.1 multibyte     string conversion. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a     denial of service, or execute arbitrary code. (CVE-2026-7383)

    Bhabani Sankar Das discovered that OpenSSL had an out-of-bounds read in CMS password-based decryption. An     attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service.
    (CVE-2026-9076)

Tenable has extracted the preceding description block directly from the Ubuntu 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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot     interface, the application-supplied initialisation vector (IV) is silently discarded. Impact summary:
    Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by     the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to     compute the authentication tag, the tag depends only on the (key, IV) pair and not on the plaintext or     ciphertext, allowing universal forgery of arbitrary ciphertext from a single captured message. OpenSSL     provides two ways to drive a cipher: the documented streaming interface (EVP_CipherUpdate /     EVP_CipherFinal_ex) and a lower-level one-shot, EVP_Cipher(), whose documentation explicitly recommends     against use by applications in favour of EVP_CipherUpdate() and EVP_CipherFinal_ex(). The OCB provider's     streaming handler flushes the application-supplied IV into the OCB context before processing data; the     one-shot handler did not. Every call to EVP_Cipher() on an AES-OCB context therefore ran with the all-zero     key-derived offset state left by cipher initialisation, regardless of the caller's IV. If     EVP_EncryptFinal_ex() is subsequently used to obtain the authentication tag, the deferred IV setup runs at     that point and clears the running checksum that should have been accumulated over the plaintext. The     resulting tag is a function of (key, IV) only and verifies against any ciphertext produced under the same     (key, IV) pair. The OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a TLS cipher suite, and     libssl does not call EVP_Cipher() in any case. Applications that drive AES-OCB through the documented     streaming AEAD API (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected. Only applications that     combine the AES-OCB cipher with the EVP_Cipher() one-shot API are vulnerable. The FIPS modules in 4.0,     3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as AES-OCB is outside the OpenSSL FIPS module     boundary. (CVE-2026-45445)

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

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

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6335-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     June 09, 2026                         https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : openssl     CVE ID         : CVE-2026-7383 CVE-2026-9076 CVE-2026-34180 CVE-2026-34181                      CVE-2026-34182 CVE-2026-34183 CVE-2026-42764 CVE-2026-42766                      CVE-2026-42767 CVE-2026-42768 CVE-2026-42769 CVE-2026-42770                      CVE-2026-45445 CVE-2026-45446 CVE-2026-45447

    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/20260609.txt

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

    For the stable distribution (trixie), these problems have been fixed in     version 3.5.6-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.0.21. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.0.21 advisory.

  - 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: 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 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: The implementations of AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) mishandle the     authentication of AAD (Additional Authenticated Data) with an empty ciphertext allowing a forgery of such     messages. Impact summary: An attacker can forge empty messages with arbitrary AAD to the victim's     application using these ciphers. AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) are nonce-misuse-resistant     AEAD modes: they accept a key, nonce, optional AAD (bytes that are authenticated but not encrypted), and     plaintext, and produces ciphertext plus a 16-byte tag. On decrypt, `EVP_DecryptFinal_ex()` is documented     to return success only if the tag is verified succesfully. In OpenSSL's provider implementation of these     ciphers, the expected tag is computed only when decryption function is invoked with non-empty data. If the     caller supplies AAD and then calls `EVP_DecryptFinal_ex()` without invocation of the ciphertext update,     which can happen when the received ciphertext length is zero, the tag is never recalculated and still     holds its all-zeros value. When AES-GCM-SIV is used, an attacker who sends arbitrary AAD, empty     ciphertext, and all-zeros tag passes authentication under any key they do not know, single-shot. When AES-     SIV is used, for mounting the attack it's necessary for the application to reuse the decryption context     without resetting the key. AES-SIV is implemented since OpenSSL 3.0. AES-GCM-SIV is implemented since     OpenSSL 3.2. No protocols implemented in OpenSSL itself (TLS/CMS/PKCS7/HPKE/QUIC) support either AES-GCM-     SIV or AES-SIV. To mount an attack, the applications must implement their own protocol and use the EVP     interface. Also they must skip the ciphertext update when a message with an empty ciphertext arrives. The     FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as these algorithms are not     FIPS approved and the affected code is outside the OpenSSL FIPS module boundary. (CVE-2026-45446)

  - Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot     interface, the application-supplied initialisation vector (IV) is silently discarded. Impact summary:
    Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by     the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to     compute the authentication tag, the tag depends only on the (key, IV) pair and not on the plaintext or     ciphertext, allowing universal forgery of arbitrary ciphertext from a single captured message. OpenSSL     provides two ways to drive a cipher: the documented streaming interface (EVP_CipherUpdate /     EVP_CipherFinal_ex) and a lower-level one-shot, EVP_Cipher(), whose documentation explicitly recommends     against use by applications in favour of EVP_CipherUpdate() and EVP_CipherFinal_ex(). The OCB provider's     streaming handler flushes the application-supplied IV into the OCB context before processing data; the     one-shot handler did not. Every call to EVP_Cipher() on an AES-OCB context therefore ran with the all-zero     key-derived offset state left by cipher initialisation, regardless of the caller's IV. If     EVP_EncryptFinal_ex() is subsequently used to obtain the authentication tag, the deferred IV setup runs at     that point and clears the running checksum that should have been accumulated over the plaintext. The     resulting tag is a function of (key, IV) only and verifies against any ciphertext produced under the same     (key, IV) pair. The OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a TLS cipher suite, and     libssl does not call EVP_Cipher() in any case. Applications that drive AES-OCB through the documented     streaming AEAD API (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected. Only applications that     combine the AES-OCB cipher with the EVP_Cipher() one-shot API are vulnerable. The FIPS modules in 4.0,     3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as AES-OCB is outside the OpenSSL FIPS module     boundary. (CVE-2026-45445)

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

  - 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: 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 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: The implementations of AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) mishandle the     authentication of AAD (Additional Authenticated Data) with an empty ciphertext allowing a forgery of such     messages. Impact summary: An attacker can forge empty messages with arbitrary AAD to the victim's     application using these ciphers. AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) are nonce-misuse-resistant     AEAD modes: they accept a key, nonce, optional AAD (bytes that are authenticated but not encrypted), and     plaintext, and produces ciphertext plus a 16-byte tag. On decrypt, `EVP_DecryptFinal_ex()` is documented     to return success only if the tag is verified succesfully. In OpenSSL's provider implementation of these     ciphers, the expected tag is computed only when decryption function is invoked with non-empty data. If the     caller supplies AAD and then calls `EVP_DecryptFinal_ex()` without invocation of the ciphertext update,     which can happen when the received ciphertext length is zero, the tag is never recalculated and still     holds its all-zeros value. When AES-GCM-SIV is used, an attacker who sends arbitrary AAD, empty     ciphertext, and all-zeros tag passes authentication under any key they do not know, single-shot. When AES-     SIV is used, for mounting the attack it's necessary for the application to reuse the decryption context     without resetting the key. AES-SIV is implemented since OpenSSL 3.0. AES-GCM-SIV is implemented since     OpenSSL 3.2. No protocols implemented in OpenSSL itself (TLS/CMS/PKCS7/HPKE/QUIC) support either AES-GCM-     SIV or AES-SIV. To mount an attack, the applications must implement their own protocol and use the EVP     interface. Also they must skip the ciphertext update when a message with an empty ciphertext arrives. The     FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as these algorithms are not     FIPS approved and the affected code is outside the OpenSSL FIPS module boundary. (CVE-2026-45446)

  - Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot     interface, the application-supplied initialisation vector (IV) is silently discarded. Impact summary:
    Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by     the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to     compute the authentication tag, the tag depends only on the (key, IV) pair and not on the plaintext or     ciphertext, allowing universal forgery of arbitrary ciphertext from a single captured message. OpenSSL     provides two ways to drive a cipher: the documented streaming interface (EVP_CipherUpdate /     EVP_CipherFinal_ex) and a lower-level one-shot, EVP_Cipher(), whose documentation explicitly recommends     against use by applications in favour of EVP_CipherUpdate() and EVP_CipherFinal_ex(). The OCB provider's     streaming handler flushes the application-supplied IV into the OCB context before processing data; the     one-shot handler did not. Every call to EVP_Cipher() on an AES-OCB context therefore ran with the all-zero     key-derived offset state left by cipher initialisation, regardless of the caller's IV. If     EVP_EncryptFinal_ex() is subsequently used to obtain the authentication tag, the deferred IV setup runs at     that point and clears the running checksum that should have been accumulated over the plaintext. The     resulting tag is a function of (key, IV) only and verifies against any ciphertext produced under the same     (key, IV) pair. The OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a TLS cipher suite, and     libssl does not call EVP_Cipher() in any case. Applications that drive AES-OCB through the documented     streaming AEAD API (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected. Only applications that     combine the AES-OCB cipher with the EVP_Cipher() one-shot API are vulnerable. The FIPS modules in 4.0,     3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as AES-OCB is outside the OpenSSL FIPS module     boundary. (CVE-2026-45445)

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

  - 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: 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 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: The implementations of AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) mishandle the     authentication of AAD (Additional Authenticated Data) with an empty ciphertext allowing a forgery of such     messages. Impact summary: An attacker can forge empty messages with arbitrary AAD to the victim's     application using these ciphers. AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) are nonce-misuse-resistant     AEAD modes: they accept a key, nonce, optional AAD (bytes that are authenticated but not encrypted), and     plaintext, and produces ciphertext plus a 16-byte tag. On decrypt, `EVP_DecryptFinal_ex()` is documented     to return success only if the tag is verified succesfully. In OpenSSL's provider implementation of these     ciphers, the expected tag is computed only when decryption function is invoked with non-empty data. If the     caller supplies AAD and then calls `EVP_DecryptFinal_ex()` without invocation of the ciphertext update,     which can happen when the received ciphertext length is zero, the tag is never recalculated and still     holds its all-zeros value. When AES-GCM-SIV is used, an attacker who sends arbitrary AAD, empty     ciphertext, and all-zeros tag passes authentication under any key they do not know, single-shot. When AES-     SIV is used, for mounting the attack it's necessary for the application to reuse the decryption context     without resetting the key. AES-SIV is implemented since OpenSSL 3.0. AES-GCM-SIV is implemented since     OpenSSL 3.2. No protocols implemented in OpenSSL itself (TLS/CMS/PKCS7/HPKE/QUIC) support either AES-GCM-     SIV or AES-SIV. To mount an attack, the applications must implement their own protocol and use the EVP     interface. Also they must skip the ciphertext update when a message with an empty ciphertext arrives. The     FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as these algorithms are not     FIPS approved and the affected code is outside the OpenSSL FIPS module boundary. (CVE-2026-45446)

  - Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot     interface, the application-supplied initialisation vector (IV) is silently discarded. Impact summary:
    Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by     the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to     compute the authentication tag, the tag depends only on the (key, IV) pair and not on the plaintext or     ciphertext, allowing universal forgery of arbitrary ciphertext from a single captured message. OpenSSL     provides two ways to drive a cipher: the documented streaming interface (EVP_CipherUpdate /     EVP_CipherFinal_ex) and a lower-level one-shot, EVP_Cipher(), whose documentation explicitly recommends     against use by applications in favour of EVP_CipherUpdate() and EVP_CipherFinal_ex(). The OCB provider's     streaming handler flushes the application-supplied IV into the OCB context before processing data; the     one-shot handler did not. Every call to EVP_Cipher() on an AES-OCB context therefore ran with the all-zero     key-derived offset state left by cipher initialisation, regardless of the caller's IV. If     EVP_EncryptFinal_ex() is subsequently used to obtain the authentication tag, the deferred IV setup runs at     that point and clears the running checksum that should have been accumulated over the plaintext. The     resulting tag is a function of (key, IV) only and verifies against any ciphertext produced under the same     (key, IV) pair. The OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a TLS cipher suite, and     libssl does not call EVP_Cipher() in any case. Applications that drive AES-OCB through the documented     streaming AEAD API (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected. Only applications that     combine the AES-OCB cipher with the EVP_Cipher() one-shot API are vulnerable. The FIPS modules in 4.0,     3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as AES-OCB is outside the OpenSSL FIPS module     boundary. (CVE-2026-45445)

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

  - 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: 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 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: The implementations of AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) mishandle the     authentication of AAD (Additional Authenticated Data) with an empty ciphertext allowing a forgery of such     messages. Impact summary: An attacker can forge empty messages with arbitrary AAD to the victim's     application using these ciphers. AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) are nonce-misuse-resistant     AEAD modes: they accept a key, nonce, optional AAD (bytes that are authenticated but not encrypted), and     plaintext, and produces ciphertext plus a 16-byte tag. On decrypt, `EVP_DecryptFinal_ex()` is documented     to return success only if the tag is verified succesfully. In OpenSSL's provider implementation of these     ciphers, the expected tag is computed only when decryption function is invoked with non-empty data. If the     caller supplies AAD and then calls `EVP_DecryptFinal_ex()` without invocation of the ciphertext update,     which can happen when the received ciphertext length is zero, the tag is never recalculated and still     holds its all-zeros value. When AES-GCM-SIV is used, an attacker who sends arbitrary AAD, empty     ciphertext, and all-zeros tag passes authentication under any key they do not know, single-shot. When AES-     SIV is used, for mounting the attack it's necessary for the application to reuse the decryption context     without resetting the key. AES-SIV is implemented since OpenSSL 3.0. AES-GCM-SIV is implemented since     OpenSSL 3.2. No protocols implemented in OpenSSL itself (TLS/CMS/PKCS7/HPKE/QUIC) support either AES-GCM-     SIV or AES-SIV. To mount an attack, the applications must implement their own protocol and use the EVP     interface. Also they must skip the ciphertext update when a message with an empty ciphertext arrives. The     FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as these algorithms are not     FIPS approved and the affected code is outside the OpenSSL FIPS module boundary. (CVE-2026-45446)

  - Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot     interface, the application-supplied initialisation vector (IV) is silently discarded. Impact summary:
    Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by     the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to     compute the authentication tag, the tag depends only on the (key, IV) pair and not on the plaintext or     ciphertext, allowing universal forgery of arbitrary ciphertext from a single captured message. OpenSSL     provides two ways to drive a cipher: the documented streaming interface (EVP_CipherUpdate /     EVP_CipherFinal_ex) and a lower-level one-shot, EVP_Cipher(), whose documentation explicitly recommends     against use by applications in favour of EVP_CipherUpdate() and EVP_CipherFinal_ex(). The OCB provider's     streaming handler flushes the application-supplied IV into the OCB context before processing data; the     one-shot handler did not. Every call to EVP_Cipher() on an AES-OCB context therefore ran with the all-zero     key-derived offset state left by cipher initialisation, regardless of the caller's IV. If     EVP_EncryptFinal_ex() is subsequently used to obtain the authentication tag, the deferred IV setup runs at     that point and clears the running checksum that should have been accumulated over the plaintext. The     resulting tag is a function of (key, IV) only and verifies against any ciphertext produced under the same     (key, IV) pair. The OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a TLS cipher suite, and     libssl does not call EVP_Cipher() in any case. Applications that drive AES-OCB through the documented     streaming AEAD API (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected. Only applications that     combine the AES-OCB cipher with the EVP_Cipher() one-shot API are vulnerable. The FIPS modules in 4.0,     3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as AES-OCB is outside the OpenSSL FIPS module     boundary. (CVE-2026-45445)

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

  - 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: 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 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: The implementations of AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) mishandle the     authentication of AAD (Additional Authenticated Data) with an empty ciphertext allowing a forgery of such     messages. Impact summary: An attacker can forge empty messages with arbitrary AAD to the victim's     application using these ciphers. AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) are nonce-misuse-resistant     AEAD modes: they accept a key, nonce, optional AAD (bytes that are authenticated but not encrypted), and     plaintext, and produces ciphertext plus a 16-byte tag. On decrypt, `EVP_DecryptFinal_ex()` is documented     to return success only if the tag is verified succesfully. In OpenSSL's provider implementation of these     ciphers, the expected tag is computed only when decryption function is invoked with non-empty data. If the     caller supplies AAD and then calls `EVP_DecryptFinal_ex()` without invocation of the ciphertext update,     which can happen when the received ciphertext length is zero, the tag is never recalculated and still     holds its all-zeros value. When AES-GCM-SIV is used, an attacker who sends arbitrary AAD, empty     ciphertext, and all-zeros tag passes authentication under any key they do not know, single-shot. When AES-     SIV is used, for mounting the attack it's necessary for the application to reuse the decryption context     without resetting the key. AES-SIV is implemented since OpenSSL 3.0. AES-GCM-SIV is implemented since     OpenSSL 3.2. No protocols implemented in OpenSSL itself (TLS/CMS/PKCS7/HPKE/QUIC) support either AES-GCM-     SIV or AES-SIV. To mount an attack, the applications must implement their own protocol and use the EVP     interface. Also they must skip the ciphertext update when a message with an empty ciphertext arrives. The     FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as these algorithms are not     FIPS approved and the affected code is outside the OpenSSL FIPS module boundary. (CVE-2026-45446)

  - Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot     interface, the application-supplied initialisation vector (IV) is silently discarded. Impact summary:
    Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by     the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to     compute the authentication tag, the tag depends only on the (key, IV) pair and not on the plaintext or     ciphertext, allowing universal forgery of arbitrary ciphertext from a single captured message. OpenSSL     provides two ways to drive a cipher: the documented streaming interface (EVP_CipherUpdate /     EVP_CipherFinal_ex) and a lower-level one-shot, EVP_Cipher(), whose documentation explicitly recommends     against use by applications in favour of EVP_CipherUpdate() and EVP_CipherFinal_ex(). The OCB provider's     streaming handler flushes the application-supplied IV into the OCB context before processing data; the     one-shot handler did not. Every call to EVP_Cipher() on an AES-OCB context therefore ran with the all-zero     key-derived offset state left by cipher initialisation, regardless of the caller's IV. If     EVP_EncryptFinal_ex() is subsequently used to obtain the authentication tag, the deferred IV setup runs at     that point and clears the running checksum that should have been accumulated over the plaintext. The     resulting tag is a function of (key, IV) only and verifies against any ciphertext produced under the same     (key, IV) pair. The OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a TLS cipher suite, and     libssl does not call EVP_Cipher() in any case. Applications that drive AES-OCB through the documented     streaming AEAD API (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected. Only applications that     combine the AES-OCB cipher with the EVP_Cipher() one-shot API are vulnerable. The FIPS modules in 4.0,     3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as AES-OCB is outside the OpenSSL FIPS module     boundary. (CVE-2026-45445)

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
322070	Amazon Linux 2023 : openssl, openssl-devel, openssl-fips-provider-latest (ALAS2023-2026-1853)	Nessus	Amazon Linux Local Security Checks	critical
321593	SUSE SLES15 Security Update : openssl-3 (SUSE-SU-2026:2397-1)	Nessus	SuSE Local Security Checks	high
321589	SUSE SLES15 Security Update : openssl-3 (SUSE-SU-2026:2393-1)	Nessus	SuSE Local Security Checks	critical
321398	Photon OS 4.0: Openssl PHSA-2026-4.0-1031	Nessus	PhotonOS Local Security Checks	critical
321207	Photon OS 5.0: Openssl PHSA-2026-5.0-0874	Nessus	PhotonOS Local Security Checks	critical
320952	RockyLinux 10 : openssl (RLSA-2026:25237)	Nessus	Rocky Linux Local Security Checks	critical
320936	RockyLinux 9 : openssl (RLSA-2026:25239)	Nessus	Rocky Linux Local Security Checks	critical
320770	Fedora 44 : openssl (2026-228373a496)	Nessus	Fedora Local Security Checks	critical
320690	AlmaLinux 10 : openssl (ALSA-2026:25237)	Nessus	Alma Linux Local Security Checks	critical
320634	RHEL 9 : openssl (RHSA-2026:25239)	Nessus	Red Hat Local Security Checks	critical
320629	RHEL 10 : openssl (RHSA-2026:25237)	Nessus	Red Hat Local Security Checks	critical
320568	FreeBSD : OpenSSL -- Multiple vulnerabilities (259b562f-64ab-11f1-8607-8447094a420f)	Nessus	FreeBSD Local Security Checks	critical
320460	FreeBSD : FreeBSD -- Multiple vulnerabilities in OpenSSL (a57fe2c1-6476-11f1-958d-bc241121aa0a)	Nessus	FreeBSD Local Security Checks	critical
320403	Ubuntu 22.04 LTS / 24.04 LTS / 25.10 / 26.04 LTS : OpenSSL vulnerabilities (USN-8414-1)	Nessus	Ubuntu Local Security Checks	critical
320335	Linux Distros Unpatched Vulnerability : CVE-2026-45445	Nessus	Misc.	high
320216	Debian dsa-6335 : libcrypto3-udeb - security update	Nessus	Debian Local Security Checks	critical
320142	OpenSSL 3.0.0 < 3.0.21 Multiple Vulnerabilities	Nessus	Web Servers	critical
320140	OpenSSL 4.0.0 < 4.0.1 Multiple Vulnerabilities	Nessus	Web Servers	critical
320138	OpenSSL 3.4.0 < 3.4.6 Multiple Vulnerabilities	Nessus	Web Servers	critical
320136	OpenSSL 3.5.0 < 3.5.7 Multiple Vulnerabilities	Nessus	Web Servers	critical
320135	OpenSSL 3.6.0 < 3.6.3 Multiple Vulnerabilities	Nessus	Web Servers	critical

Detections

Analytics

CVE-2026-45445

high

Tenable Plugins

critical

high

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

high

critical

critical

critical

critical

critical

critical