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

  - Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg     parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can     contain a parameter of a different type, which is then dereferenced as an invalid pointer. Impact summary:
    A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-     protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a     Denial of Service. CWE: CWE-476: NULL Pointer Dereference Description: When verifying the password-based     MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with     X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to     an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The     parameter type returned by X509_ALGOR_get0() was never consulted. This happens during protection     verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only     precondition is that PBM verification is reachable. On the server side this is reached from     OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected     messages, and on the client side from CMP response validation against a malicious or on-path (MITM)     server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled     memory write, and no path to code execution. CMP is a specialized feature that an application must     explicitly enable. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules     are affected by this CVE. (CVE-2026-63076)

  - Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success     without verifying the supplied authentication tag when the operation is finalized by calling the     EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and     expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of     Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot     encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for     AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was     passed to the function. The callers of this function might believe that a successful return indicates a     valid AEAD tag for these ciphers, even when that has not truly been validated in this case. FIPS impact:
    no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms     are not FIPS approved and thus not implemented in the FIPS module. (CVE-2026-75803)

  - Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets     while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the     lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause     connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially     with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without     Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no     requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself     not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames     regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives     the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by     sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like     legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer,     potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of     the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only     packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is     outside the FIPS module boundary. (CVE-2026-63075)

  - Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates     (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a     server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious     client may flood a CMP server with requests driving this growth. Impact summary: Users utilizing a CMP     server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory     growth in the event a malicious client repeatedly sends requests containing unique extra certificates,     which may lead to OOM conditions. CWE: CWE-770: Allocation of Resources Without Limits or Throttling     Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is     rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This     exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends     messages intending to be rejected with a large list of additional certificates repeatedly, forcing the     server to store them indefinitely. The issue was fixed by removing the added extra certs if the message is     rejected, using the same method as when the context is configured to not do caching at all. FIPS impact:
    no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.
    (CVE-2026-63074)

  - Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name     directly as the format string to `ERR_raise_data()`. Impact summary: A malicious or intercepted CMP     endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose     subject becomes the default expected sender. CWE: CWE-134 (Use of Externally-Controlled Format String)     Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-     supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument     to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as CN=%s%n reaches     BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is     only reached when the caller configures an expected sender or pins a server certificate, which is the     normal configuration for a CMP client validating server responses. Since the attacker controls the format     string but none of the variadic arguments, such specifiers as %s and %n dereference or write through     unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the     response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write,     arbitrary-address read, or reliable path to remote code execution. FIPS impact: no No FIPS modules are     affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.
    (CVE-2026-63073)

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

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

    * openssl: OpenSSL: Denial of Service via unbounded memory growth in QUIC server (CVE-2026-14456)

    * openssl: QUIC server may trigger double free when processing INITIAL packet (CVE-2026-18798)

    * openssl: heap buffer overflow in CMS key unwrapping (CVE-2026-63072)

    * openssl: invalid pointer dereference in CMP server via crafted protectionAlg (CVE-2026-63076)

    * openssl: RPK server signature algorithm selection can dereference a missing certificate (CVE-2026-14457)

    * openssl: excessive memory use buffering DTLS records for a future epoch (CVE-2026-54874)

    * openssl: untrusted sender DN used as format string in CMP response validation (CVE-2026-63073)

    * openssl: CMP indefinite cache growth of ExtraCerts (CVE-2026-63074)

    * openssl: QUIC ACK-only packet retention can cause memory exhaustion (CVE-2026-63075)

    Bug Fix(es) and Enhancement(s):

    * openssl: HollowByte remote memory-exhaustion DoS fix may be missing [Rocky Linux 10.2.z] (JIRA:Rocky     Linux-212362)

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 version of OpenSSL installed on the remote host is prior to 3.4.7. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.4.7 advisory.

  - Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg     parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can     contain a parameter of a different type, which is then dereferenced as an invalid pointer. Impact summary:
    A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-     protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a     Denial of Service. CWE: CWE-476: NULL Pointer Dereference Description: When verifying the password-based     MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with     X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to     an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The     parameter type returned by X509_ALGOR_get0() was never consulted. This happens during protection     verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only     precondition is that PBM verification is reachable. On the server side this is reached from     OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected     messages, and on the client side from CMP response validation against a malicious or on-path (MITM)     server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled     memory write, and no path to code execution. CMP is a specialized feature that an application must     explicitly enable. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules     are affected by this CVE. (CVE-2026-63076)

  - Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success     without verifying the supplied authentication tag when the operation is finalized by calling the     EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and     expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of     Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot     encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for     AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was     passed to the function. The callers of this function might believe that a successful return indicates a     valid AEAD tag for these ciphers, even when that has not truly been validated in this case. FIPS impact:
    no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms     are not FIPS approved and thus not implemented in the FIPS module. (CVE-2026-75803)

  - Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets     while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the     lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause     connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially     with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without     Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no     requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself     not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames     regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives     the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by     sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like     legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer,     potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of     the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only     packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is     outside the FIPS module boundary. (CVE-2026-63075)

  - Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates     (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a     server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious     client may flood a CMP server with requests driving this growth. Impact summary: Users utilizing a CMP     server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory     growth in the event a malicious client repeatedly sends requests containing unique extra certificates,     which may lead to OOM conditions. CWE: CWE-770: Allocation of Resources Without Limits or Throttling     Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is     rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This     exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends     messages intending to be rejected with a large list of additional certificates repeatedly, forcing the     server to store them indefinitely. The issue was fixed by removing the added extra certs if the message is     rejected, using the same method as when the context is configured to not do caching at all. FIPS impact:
    no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.
    (CVE-2026-63074)

  - Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name     directly as the format string to `ERR_raise_data()`. Impact summary: A malicious or intercepted CMP     endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose     subject becomes the default expected sender. CWE: CWE-134 (Use of Externally-Controlled Format String)     Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-     supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument     to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as CN=%s%n reaches     BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is     only reached when the caller configures an expected sender or pins a server certificate, which is the     normal configuration for a CMP client validating server responses. Since the attacker controls the format     string but none of the variadic arguments, such specifiers as %s and %n dereference or write through     unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the     response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write,     arbitrary-address read, or reliable path to remote code execution. FIPS impact: no No FIPS modules are     affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.
    (CVE-2026-63073)

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: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only     the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur     when the remote peer solicits raw public keys and also sends the typically omitted     signature_algorithms_cert TLS extension. Impact summary: The impact is limited to a possible Denial of     Service as a result of an application abort, no data disclosure or remote command execution are possible.
    CWE: CWE-476: NULL Pointer Dereference Description: While a passing comment in sample code in the     documentation suggests that key-only RPK configurations are supported, the best-practice RPK configuration     is to always configure a corresponding certificate (possibly self-signed or signed by any convenient CA).
    When the private key is configured along with a matching certificate, the signature_algorithms_cert     extension is handled reliably even without the fix, and peer clients or servers that don't support raw     public keys may be able to complete a TLS connection by pinning or verifying the corresponding certificate     or its public key. Deployments that prefer to configure just a private key with no certificate need to     upgrade to an updated release as noted below. FIPS impact: no No FIPS modules are affected by this issue,     as the SSL protocol implementation is outside the OpenSSL FIPS module boundary. (CVE-2026-14457)

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

  - Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped     key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports,     causing an 8-byte out-of-bounds heap write. Impact summary: An attacker who supplies a crafted CMS message     can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with     CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. CWE: CWE-787: Out-of-     bounds Write Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping     allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and     change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the     unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation),     the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure. The write is a     fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special     configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap     corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the     worst case so a failed unwrap cannot write past the allocation. FIPS impact: no As the CMS code lives     outside the FIPS module boundary, no FIPS modules are affected by this CVE. (CVE-2026-63072)

  - Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets     while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the     lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause     connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially     with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without     Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no     requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself     not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames     regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives     the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by     sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like     legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer,     potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of     the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only     packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is     outside the FIPS module boundary. (CVE-2026-63075)

  - Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success     without verifying the supplied authentication tag when the operation is finalized by calling the     EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and     expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of     Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot     encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for     AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was     passed to the function. The callers of this function might believe that a successful return indicates a     valid AEAD tag for these ciphers, even when that has not truly been validated in this case. FIPS impact:
    no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms     are not FIPS approved and thus not implemented in the FIPS module. (CVE-2026-75803)

  - Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg     parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can     contain a parameter of a different type, which is then dereferenced as an invalid pointer. Impact summary:
    A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-     protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a     Denial of Service. CWE: CWE-476: NULL Pointer Dereference Description: When verifying the password-based     MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with     X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to     an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The     parameter type returned by X509_ALGOR_get0() was never consulted. This happens during protection     verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only     precondition is that PBM verification is reachable. On the server side this is reached from     OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected     messages, and on the client side from CMP response validation against a malicious or on-path (MITM)     server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled     memory write, and no path to code execution. CMP is a specialized feature that an application must     explicitly enable. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules     are affected by this CVE. (CVE-2026-63076)

  - Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates     (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a     server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious     client may flood a CMP server with requests driving this growth. Impact summary: Users utilizing a CMP     server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory     growth in the event a malicious client repeatedly sends requests containing unique extra certificates,     which may lead to OOM conditions. CWE: CWE-770: Allocation of Resources Without Limits or Throttling     Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is     rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This     exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends     messages intending to be rejected with a large list of additional certificates repeatedly, forcing the     server to store them indefinitely. The issue was fixed by removing the added extra certs if the message is     rejected, using the same method as when the context is configured to not do caching at all. FIPS impact:
    no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.
    (CVE-2026-63074)

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

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

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6465-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     August 25, 2026                       https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : openssl     CVE ID         : CVE-2026-14456 CVE-2026-14457 CVE-2026-18798 CVE-2026-54874                      CVE-2026-63072 CVE-2026-63073 CVE-2026-63074 CVE-2026-63075                      CVE-2026-63076 CVE-2026-75803     Debian Bug     : 1144615 1145172

    Multiple vulnerabilities have been discovered in OpenSSL, a Secure     Sockets Layer toolkit, which may result in denial of service.

    Additional details can be found in the upstream advisories:
    https://openssl-library.org/news/secadv/20260813.txt     https://openssl-library.org/news/secadv/20260825.txt

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

    We recommend that you upgrade your openssl packages.

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

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

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

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

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

The remote AlmaLinux 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2026:67154 advisory.

    * openssl: OpenSSL: Denial of Service via unbounded memory growth in QUIC server (CVE-2026-14456)
      * openssl: QUIC server may trigger double free when processing INITIAL packet (CVE-2026-18798)
      * openssl: heap buffer overflow in CMS key unwrapping (CVE-2026-63072)
      * openssl: invalid pointer dereference in CMP server via crafted protectionAlg (CVE-2026-63076)
      * openssl: RPK server signature algorithm selection can dereference a missing certificate     (CVE-2026-14457)
      * openssl: excessive memory use buffering DTLS records for a future epoch (CVE-2026-54874)
      * openssl: untrusted sender DN used as format string in CMP response validation (CVE-2026-63073)
      * openssl: CMP indefinite cache growth of ExtraCerts (CVE-2026-63074)
      * openssl: QUIC ACK-only packet retention can cause memory exhaustion (CVE-2026-63075)


    Bug Fix(es) and Enhancement(s):

      * openssl: HollowByte remote memory-exhaustion DoS fix may be missing [AlmaLinux 10.2.z]     (JIRA:AlmaLinux-212362)

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

    * openssl: OpenSSL: Denial of Service via unbounded memory growth in QUIC server (CVE-2026-14456)

    * openssl: QUIC server may trigger double free when processing INITIAL packet (CVE-2026-18798)

    * openssl: heap buffer overflow in CMS key unwrapping (CVE-2026-63072)

    * openssl: invalid pointer dereference in CMP server via crafted protectionAlg (CVE-2026-63076)

    * openssl: RPK server signature algorithm selection can dereference a missing certificate (CVE-2026-14457)

    * openssl: excessive memory use buffering DTLS records for a future epoch (CVE-2026-54874)

    * openssl: untrusted sender DN used as format string in CMP response validation (CVE-2026-63073)

    * openssl: CMP indefinite cache growth of ExtraCerts (CVE-2026-63074)

    * openssl: QUIC ACK-only packet retention can cause memory exhaustion (CVE-2026-63075)

    Bug Fix(es) and Enhancement(s):

    * openssl: HollowByte remote memory-exhaustion DoS fix may be missing [Rocky Linux 9.8.z] (JIRA:Rocky     Linux-232828)

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

    August 2026 release.

    - CVE-2026-14456: unbounded memory growth in QUIC server incoming channel queue (bsc#1274791).
    - CVE-2026-14457: RPK server signature algorithm selection can dereference a missing certificate     (bsc#1274792).
    - CVE-2026-18798: QUIC server may trigger double free when processing INITIAL packet (bsc#1274777).
    - CVE-2026-34181: PKCS#12 files with PBMAC1 are accepted with short HMAC keys (bsc#1266343).
    - CVE-2026-54874: excessive Memory Use Buffering DTLS Records for a Future Epoch (bsc#1274795).
    - CVE-2026-63072: heap buffer overflow in CMS key unwrapping (bsc#1274788).
    - CVE-2026-63073: untrusted sender DN used as format string in CMP response validation (bsc#1274796).
    - CVE-2026-63074: CMP indefinite cache growth of `ExtraCerts` (bsc#1274797).
    - CVE-2026-63075: QUIC ACK-only packet retention can cause memory exhaustion (bsc#1274798).
    - CVE-2026-63076: invalid pointer dereference in CMP server via crafted `protectionAlg` (bsc#1274790).
    - CVE-2026-75803: AEAD forgeries with empty ciphertext when using `EVP_Cipher()` (bsc#1275837).

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 Ubuntu 22.04 LTS / 24.04 LTS / 26.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-8678-1 advisory.

    It was discovered that OpenSSL incorrectly handled the QUIC server incoming channel queue. 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 26.04 LTS. (CVE-2026-14456)

    It was discovered that OpenSSL incorrectly handled signature algorithm selection when using Raw Public     Keys. A remote attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of     service. This issue only affected Ubuntu 26.04 LTS. (CVE-2026-14457)

    It was discovered that OpenSSL incorrectly handled QUIC INITIAL packet processing. A remote attacker could     possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. This issue only     affected Ubuntu 26.04 LTS. (CVE-2026-18798)

    It was discovered that OpenSSL incorrectly handled buffering of DTLS records for a future epoch. A remote     attacker could possibly use this issue to cause OpenSSL to use excessive resources, leading to a denial of     service. (CVE-2026-54874)

    It was discovered that OpenSSL incorrectly handled CMS key unwrapping. A remote attacker could possibly     use this issue to cause a heap buffer overflow, leading to a denial of service or arbitrary code     execution. (CVE-2026-63072)

    It was discovered that OpenSSL incorrectly validated the sender distinguished name in CMP response     messages. A remote attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial     of service. This issue only affected Ubuntu 26.04 LTS. (CVE-2026-63073)

    It was discovered that OpenSSL incorrectly limited the growth of an internal certificate cache used during     CMP operations. A remote attacker could possibly use this issue to cause OpenSSL to use excessive     resources, leading to a denial of service. (CVE-2026-63074)

    It was discovered that OpenSSL incorrectly handled QUIC ACK-only packet retention. 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 26.04 LTS. (CVE-2026-63075)

    It was discovered that OpenSSL incorrectly handled CMP protection algorithm validation. A remote attacker     could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service.
    (CVE-2026-63076)

    It was discovered that OpenSSL incorrectly verified authentication tags when using certain AEAD ciphers     via the EVP_Cipher() interface. An attacker could possibly use this issue to perform AEAD forgery attacks.
    (CVE-2026-75803)

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 Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ ciqsa-2026_1764 advisory.

    This advisory aggregates security fixes for the openssl SRPM in CIQ LTS 9.6. It addresses 4 CVEs:
    CVE-2026-63075, CVE-2026-63076, CVE-2026-14457, CVE-2026-63074.

Tenable has extracted the preceding description block directly from the CIQ 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.5.8. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.5.8 advisory.

  - Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets     while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the     lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause     connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially     with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without     Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no     requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself     not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames     regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives     the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by     sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like     legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer,     potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of     the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only     packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is     outside the FIPS module boundary. (CVE-2026-63075)

  - Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg     parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can     contain a parameter of a different type, which is then dereferenced as an invalid pointer. Impact summary:
    A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-     protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a     Denial of Service. CWE: CWE-476: NULL Pointer Dereference Description: When verifying the password-based     MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with     X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to     an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The     parameter type returned by X509_ALGOR_get0() was never consulted. This happens during protection     verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only     precondition is that PBM verification is reachable. On the server side this is reached from     OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected     messages, and on the client side from CMP response validation against a malicious or on-path (MITM)     server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled     memory write, and no path to code execution. CMP is a specialized feature that an application must     explicitly enable. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules     are affected by this CVE. (CVE-2026-63076)

  - Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success     without verifying the supplied authentication tag when the operation is finalized by calling the     EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and     expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of     Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot     encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for     AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was     passed to the function. The callers of this function might believe that a successful return indicates a     valid AEAD tag for these ciphers, even when that has not truly been validated in this case. FIPS impact:
    no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms     are not FIPS approved and thus not implemented in the FIPS module. (CVE-2026-75803)

  - Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates     (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a     server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious     client may flood a CMP server with requests driving this growth. Impact summary: Users utilizing a CMP     server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory     growth in the event a malicious client repeatedly sends requests containing unique extra certificates,     which may lead to OOM conditions. CWE: CWE-770: Allocation of Resources Without Limits or Throttling     Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is     rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This     exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends     messages intending to be rejected with a large list of additional certificates repeatedly, forcing the     server to store them indefinitely. The issue was fixed by removing the added extra certs if the message is     rejected, using the same method as when the context is configured to not do caching at all. FIPS impact:
    no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.
    (CVE-2026-63074)

  - Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name     directly as the format string to `ERR_raise_data()`. Impact summary: A malicious or intercepted CMP     endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose     subject becomes the default expected sender. CWE: CWE-134 (Use of Externally-Controlled Format String)     Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-     supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument     to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as CN=%s%n reaches     BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is     only reached when the caller configures an expected sender or pins a server certificate, which is the     normal configuration for a CMP client validating server responses. Since the attacker controls the format     string but none of the variadic arguments, such specifiers as %s and %n dereference or write through     unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the     response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write,     arbitrary-address read, or reliable path to remote code execution. FIPS impact: no No FIPS modules are     affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.
    (CVE-2026-63073)

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

    * openssl: OpenSSL: Denial of Service via unbounded memory growth in QUIC server (CVE-2026-14456)
      * openssl: QUIC server may trigger double free when processing INITIAL packet (CVE-2026-18798)
      * openssl: heap buffer overflow in CMS key unwrapping (CVE-2026-63072)
      * openssl: invalid pointer dereference in CMP server via crafted protectionAlg (CVE-2026-63076)
      * openssl: RPK server signature algorithm selection can dereference a missing certificate     (CVE-2026-14457)
      * openssl: excessive memory use buffering DTLS records for a future epoch (CVE-2026-54874)
      * openssl: untrusted sender DN used as format string in CMP response validation (CVE-2026-63073)
      * openssl: CMP indefinite cache growth of ExtraCerts (CVE-2026-63074)
      * openssl: QUIC ACK-only packet retention can cause memory exhaustion (CVE-2026-63075)


    Bug Fix(es) and Enhancement(s):

      * openssl: HollowByte remote memory-exhaustion DoS fix may be missing [AlmaLinux 9.8.z]     (JIRA:AlmaLinux-232828)

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 Oracle Linux 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2026-500326 advisory.

    [3.5.8-1.0.1]
    - Replace upstream references [Orabug: 34340177]
    - Update FIPS provider name [Orabug: 35824276]

    [1:3.5.8-1]
    - Rebase to OpenSSL 3.5.8       Resolves: RHEL-242944       Resolves: RHEL-246254       Resolves: RHEL-246266       Resolves: RHEL-246306       Resolves: RHEL-246437       Resolves: RHEL-246441       Resolves: RHEL-246445       Resolves: RHEL-246449       Resolves: RHEL-246453

Tenable has extracted the preceding description block directly from the Oracle 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 Oracle Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2026-500327 advisory.

    [3.5.8-1.0.1]
    - Replace upstream references [Orabug: 34340177]

    [3.5.8.openela.0.1]
    - Add OpenELA specific changes

    [1:3.5.8-1]
    - Rebase to OpenSSL 3.5.8       Resolves: RHEL-242945       Resolves: RHEL-246260       Resolves: RHEL-246284       Resolves: RHEL-246319       Resolves: RHEL-246439       Resolves: RHEL-246443       Resolves: RHEL-246447       Resolves: RHEL-246451       Resolves: RHEL-246455

Tenable has extracted the preceding description block directly from the Oracle 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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
332717	OpenSSL 3.6.0 < 3.6.4 Multiple Vulnerabilities	Nessus	Web Servers	2026/8/5	2026/9/1	critical
345922	RockyLinux 10 : openssl (RLSA-2026:67154)	Nessus	Rocky Linux Local Security Checks	2026/9/15	2026/9/15	critical
374269	Nessus Network Monitor < 6.6.0 Multiple Vulnerabilities (TNS-2026-32)	Nessus	Misc.	2026/10/30	2026/11/2	high
339490	OpenSSL 3.4.0 < 3.4.7 Multiple Vulnerabilities	Nessus	Web Servers	2026/8/25	2026/9/1	critical
339480	Linux Distros Unpatched Vulnerability : CVE-2026-14457	Nessus	Misc.	2026/8/25	2026/11/6	high
332232	OpenSSL 4.0.0 < 4.0.2 Multiple Vulnerabilities	Nessus	Web Servers	2026/8/5	2026/9/1	critical
339549	Debian dsa-6465 : libcrypto3-udeb - security update	Nessus	Debian Local Security Checks	2026/8/25	2026/9/1	critical
345934	AlmaLinux 10 : openssl (ALSA-2026:67154)	Nessus	Alma Linux Local Security Checks	2026/9/15	2026/9/15	critical
346036	RockyLinux 9 : openssl (RLSA-2026:67165)	Nessus	Rocky Linux Local Security Checks	2026/9/15	2026/9/15	critical
348483	SUSE SLED15: libopenssl-3-devel / libopenssl-3-fips-provider / etc (SUSE-SU-2026:4039-1)	Nessus	SuSE Local Security Checks	2026/9/21	2026/9/21	critical
365402	Ubuntu 22.04 LTS / 24.04 LTS / 26.04 LTS : OpenSSL vulnerabilities (USN-8678-1)	Nessus	Ubuntu Local Security Checks	2026/10/13	2026/10/13	critical
378106	Rocky Linux 9.6 [CIQ] Security Update: openssl / openssl-devel / openssl-libs / openssl-perl Multiple Vulnerabilities (ciqsa-2026_1764)	Nessus	Rocky Linux Local Security Checks	2026/11/10	2026/11/10	high
335167	OpenSSL 3.5.0 < 3.5.8 Multiple Vulnerabilities	Nessus	Web Servers	2026/8/13	2026/9/1	critical
345932	AlmaLinux 9 : openssl (ALSA-2026:67165)	Nessus	Alma Linux Local Security Checks	2026/9/15	2026/10/26	critical
346888	Oracle Linux 10 : openssl (ELSA-2026-500326)	Nessus	Oracle Linux Local Security Checks	2026/9/17	2026/9/17	critical
348162	Oracle Linux 9 : openssl (ELSA-2026-500327)	Nessus	Oracle Linux Local Security Checks	2026/9/18	2026/9/18	critical

检测

插件搜索

critical

critical

high

critical

high

critical

critical

critical

critical

critical

critical

high

critical

critical

critical

critical