The version of Tenable Identity Exposure running on the remote host is prior to 3.93.5. It is, therefore, affected by multiple vulnerabilities according to advisory TNS-2026-16:

  - Tenable Identity Exposure contains multiple unauthenticated API endpoints under /w/api/* that expose     sensitive application configuration data including cleartext LDAP credentials, SAML configuration, user     accounts, and directory settings to unauthenticated remote attackers. Affected responses are served with     Cache-Control: public headers and without Vary: Cookie, allowing reverse proxies and CDNs to cache and     serve sensitive data to unauthenticated users even after authentication is applied. (CVE-2026-13007)

  - Inconsistent interpretation of http requests ('http request/response smuggling') in ASP.NET Core allows     an authorized attacker to bypass a security feature over a network. (CVE-2025-55315)

  - Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer     overflow on 32 bit platforms. A heap buffer overflow may lead to a crash or possibly an attacker     controlled code execution or other undefined behavior. (CVE-2026-31789)

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:1472 advisory.

    * openssl: OpenSSL: Arbitrary code execution or denial of service through crafted PKCS#12 file     (CVE-2025-11187)
      * openssl: OpenSSL: Remote code execution or Denial of Service via oversized Initialization Vector in     CMS parsing (CVE-2025-15467)
      * openssl: OpenSSL: Denial of Service via NULL pointer dereference in QUIC protocol handling     (CVE-2025-15468)
      * openssl: OpenSSL: Data integrity bypass in `openssl dgst` command due to silent truncation     (CVE-2025-15469)
      * openssl: OpenSSL: Denial of Service due to excessive memory allocation in TLS 1.3 certificate     compression (CVE-2025-66199)
      * openssl: OpenSSL: Denial of Service due to out-of-bounds write in BIO filter (CVE-2025-68160)
      * openssl: OpenSSL: Information disclosure and data tampering via specific low-level OCB     encryption/decryption calls (CVE-2025-69418)
      * openssl: OpenSSL: Arbitrary code execution due to out-of-bounds write in PKCS#12 processing     (CVE-2025-69419)
      * openssl: OpenSSL: Denial of Service via malformed PKCS#12 file processing (CVE-2025-69421)
      * openssl: OpenSSL: Denial of Service via malformed TimeStamp Response (CVE-2025-69420)
      * openssl: OpenSSL: Denial of Service due to type confusion in PKCS#12 file processing (CVE-2026-22795)
      * openssl: OpenSSL: Denial of Service via type confusion in PKCS#7 signature verification     (CVE-2026-22796)

Tenable has extracted the preceding description block directly from the 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 SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0311-1 advisory.

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

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

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

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

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

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

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

An update of the openssl package has been released.

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

    Security fixes:

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

    Other fixes:

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

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

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

The version of IBM MQ Server running on the remote host is affected by multiple vulnerabilities as referenced in the 7262259 advisory.

 - Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function. Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files. The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. (CVE-2025-69421)

 - Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation which can trigger a stack-based buffer overflow, invalid pointer or NULL pointer dereference during MAC verification. Impact summary: The stack buffer overflow or NULL pointer dereference may cause a crash leading to Denial of Service for an application that parses untrusted PKCS#12 files. The buffer overflow may also potentially enable code execution depending on platform mitigations. When verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2 salt and keylength parameters from the file are used without validation. If the value of keylength exceeds the size of the fixed stack buffer used for the derived key (64 bytes), the key derivation will overflow the buffer. The overflow length is attacker-controlled. Also, if the salt parameter is not an OCTET STRING type this can lead to invalid or NULL pointer dereference. Exploiting this issue requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For this reason the issue was assessed as Moderate severity. The FIPS modules in 3.6, 3.5 and 3.4 are not affected by this issue, as PKCS#12 processing is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue. OpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do not support PBMAC1 in PKCS#12. (CVE-2025-11187)

 - Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution. When parsing CMS (Auth)EnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack- based out-of-bounds write before any authentication or tag verification occurs. Applications and services that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME (Auth)EnvelopedData with AES- GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is required to trigger it. While exploitability to remote code execution depends on platform and toolchain mitigations, the stack-based write primitive represents a severe risk. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue. OpenSSL 1.1.1 and 1.0.2 are not affected by this issue. (CVE-2025-15467)

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

 - Issue summary: The 'openssl dgst' command-line tool silently truncates input data to 16MB when using one- shot signing algorithms and reports success instead of an error. Impact summary: A user signing or verifying files larger than 16MB with one-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire file is authenticated while trailing data beyond 16MB remains unauthenticated. When the 'openssl dgst' command is used with algorithms that only support one-shot signing (Ed25519, Ed448, ML- DSA-44, ML-DSA-65, ML-DSA-87), the input is buffered with a 16MB limit. If the input exceeds this limit, the tool silently truncates to the first 16MB and continues without signaling an error, contrary to what the documentation states. This creates an integrity gap where trailing bytes can be modified without detection if both signing and verification are performed using the same affected codepath. The issue affects only the command-line tool behavior. Verifiers that process the full message using library APIs will reject the signature, so the risk primarily affects workflows that both sign and verify with the affected 'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and library users are unaffected. The FIPS modules in 3.5 and 3.6 are not affected by this issue, as the command-line tools are outside the OpenSSL FIPS module boundary. OpenSSL 3.5 and 3.6 are vulnerable to this issue. OpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue. (CVE-2025-15469)

 - Issue summary: A TLS 1.3 connection using certificate compression can be forced to allocate a large buffer before decompression without checking against the configured certificate size limit. Impact summary: An attacker can cause per-connection memory allocations of up to approximately 22 MiB and extra CPU work, potentially leading to service degradation or resource exhaustion (Denial of Service). In affected configurations, the peer-supplied uncompressed certificate length from a CompressedCertificate message is used to grow a heap buffer prior to decompression. This length is not bounded by the max_cert_list setting, which otherwise constrains certificate message sizes. An attacker can exploit this to cause large per-connection allocations followed by handshake failure. No memory corruption or information disclosure occurs. This issue only affects builds where TLS 1.3 certificate compression is compiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression algorithm (brotli, zlib, or zstd) is available, and where the compression extension is negotiated. Both clients receiving a server CompressedCertificate and servers in mutual TLS scenarios receiving a client CompressedCertificate are affected. Servers that do not request client certificates are not vulnerable to client-initiated attacks. Users can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION to disable receiving compressed certificates. The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as the TLS implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. (CVE-2025-66199)

 - Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write. Impact summary: This out-of- bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application. The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write and that write large, newline-free data influenced by an attacker would be affected. However, the circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed as Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the BIO implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. (CVE-2025-68160)

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

 - Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
 The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker- controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue.
 (CVE-2025-69419)

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

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

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

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

  - NLnet Labs Unbound 1.19.1 up to and including version 1.25.0 has a vulnerability in the DNSSEC validator     that enables denial of service and possible remote code execution as a result of deep copying a data     structure and erroneously overwriting a destination pointer. An adversary can exploit the vulnerability by     controlling a malicious signed zone and querying a vulnerable Unbound. When DS sub-queries need to suspend     validation due to NSEC3 computational budget exhaustion (introduced in Unbound 1.19.1), Unbound deep-     copies response messages to preserve them across memory region teardown. A struct-assignment bug     overwrites the destination's pointer with the source's pointer. After the sub-query region is freed, the     resumed validator dereferences this dangling pointer, triggering a crash or potentially enabling arbitrary     code execution. Unbound 1.25.1 contains a patch with a fix to preserve the correct pointer when deep     copying the data structure. (CVE-2026-33278)

  - A vulnerability has been found in GNU Binutils 2.45. The affected element is the function elf_swap_shdr in     the library bfd/elfcode.h of the component Linker. The manipulation leads to heap-based buffer overflow.
    The attack must be carried out locally. The exploit has been disclosed to the public and may be used. The     identifier of the patch is 9ca499644a21ceb3f946d1c179c38a83be084490. To fix this issue, it is recommended     to deploy a patch. The code maintainer replied with [f]ixed for 2.46. (CVE-2025-11083)

  - A heap-based buffer overflow problem was found in glib through an incorrect calculation of buffer size in     the g_escape_uri_string() function. If the string to escape contains a very large number of unacceptable     characters (which would need escaping), the calculation of the length of the escaped string could     overflow, leading to a potential write off the end of the newly allocated string. (CVE-2025-13601)

  - Vim is an open source, command line text editor. Prior to version 9.1.1552, a path traversal issue in     Vim's tar.vim plugin can allow overwriting of arbitrary files when opening specially crafted tar archives.
    Impact is low because this exploit requires direct user interaction. However, successfully exploitation     can lead to overwriting sensitive files or placing executable code in privileged locations, depending on     the permissions of the process editing the archive. The victim must edit such a file using Vim which will     reveal the filename and the file content, a careful user may suspect some strange things going on.
    Successful exploitation could results in the ability to execute arbitrary commands on the underlying     operating system. Version 9.1.1552 contains a patch for the vulnerability. (CVE-2025-53905)

  - Vim is an open source, command line text editor. Prior to version 9.1.1551, a path traversal issue in     Vim's zip.vim plugin can allow overwriting of arbitrary files when opening specially crafted zip archives.
    Impact is low because this exploit requires direct user interaction. However, successfully exploitation     can lead to overwriting sensitive files or placing executable code in privileged locations, depending on     the permissions of the process editing the archive. The victim must edit such a file using Vim which will     reveal the filename and the file content, a careful user may suspect some strange things going on.
    Successful exploitation could results in the ability to execute arbitrary commands on the underlying     operating system. Version 9.1.1551 contains a patch for the vulnerability. (CVE-2025-53906)

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

According to its self-reported version, the Tenable Security Center running on the remote host is between 6.6.0 and 6.8.0. It is, therefore, affected by multiple vulnerabilities as referenced in the TNS-2026-19 advisory.

  - Tenable Security Center is affected by a SQL injection vulnerability. (CVE-2026-64877)

  - Double Free and possible RCE vulnerability in Apache HTTP Server with the HTTP/2 protocol. This issue     affects Apache HTTP Server: 2.4.66. Users are recommended to upgrade to version 2.4.67, which fixes the     issue. (CVE-2026-23918)

  - Stack buffer overflow in PostgreSQL module refint allows an unprivileged database user to execute     arbitrary code as the operating system user running the database. A distinct attack is possible if the     application declares a user-controlled column as a refint cascade primary key and facilitates user-     controlled updates to that column. In that case, a SQL injection allows a primary key update value     provider to execute arbitrary SQL as the database user performing the primary key update. Versions before     PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected. (CVE-2026-6637)

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

According to the versions of the openssl packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

    Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the     next BIO performs short writes can trigger a heap-based out-of-bounds write. Impact summary: This out-of-     bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service     for an application. The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL     data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS     systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write     and that write large, newline-free data influenced by an attacker would be affected. However, the     circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is     unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed     as Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the BIO     implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and     1.0.2 are vulnerable to this issue.(CVE-2025-68160)

    Issue summary: When using the low-level OCB API directly with AES-NI orbrother hardware-accelerated     code paths, inputs whose length is not a multiplebrof 16 bytes can leave the final partial block     unencrypted and unauthenticated.brbrImpact summary: The trailing 1-15 bytes of a message may     be exposed inbrcleartext on encryption and are not covered by the authentication     tag,brallowing an attacker to read or tamper with those bytes without detection.brbrThe     low-level OCB encrypt and decrypt routines in the hardware-acceleratedbrstream path process full     16-byte blocks but do not advance the input/outputbrpointers. The subsequent tail-handling code then     operates on the originalbrbase pointers, effectively reprocessing the beginning of the buffer     whilebrleaving the actual trailing bytes unprocessed. The authentication checksumbralso     excludes the true tail bytes.brbrHowever, typical OpenSSL consumers using EVP are not affected     because thebrhigher-level EVP and provider OCB implementations split inputs so that     fullbrblocks and trailing partial blocks are processed in separate calls, avoidingbrthe     problematic code path. Additionally, TLS does not use OCB ciphersuites.brThe vulnerability only     affects applications that call the low-levelbrCRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt()     functions directly withbrnon-block-aligned lengths in a single call on hardware-accelerated     builds.brFor these reasons the issue was assessed as Low severity.brbrThe FIPS modules     in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affectedbrby this issue, as OCB mode is not a FIPS-     approved algorithm.brbrOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this     issue.brbrOpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69418)

    Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a     BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before     the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have     various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass     conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the     helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the     destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes,     but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is     added to the output length without validation, causing the length to become negative. The subsequent     trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
    The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-     controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue,     PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to     provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one     zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity     according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this     issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4,     3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this     issue.(CVE-2025-69419)

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

    Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the     PKCS12_item_decrypt_d2i_ex() function. Impact summary: A NULL pointer dereference can trigger a crash     which leads to Denial of Service for an application processing PKCS#12 files. The     PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before     dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter     can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to     achieve code execution or memory disclosure. Exploiting this issue requires an attacker to provide a     malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low     severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected     by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6,     3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-69421)

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

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

Tenable has extracted the preceding description block directly from the EulerOS Virtualization openssl 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:1473 advisory.

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

    Security Fix(es):

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The remote Oracle Linux 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2026-1472 advisory.

    - Fix CVE-2025-11187 CVE-2025-15467 CVE-2025-15468 CVE-2025-15469       CVE-2025-66199 CVE-2025-68160 CVE-2025-69418 CVE-2025-69419 CVE-2025-69420       CVE-2025-69421 CVE-2026-22795 CVE-2026-22796       Resolves: RHEL-142062       Resolves: RHEL-141985       Resolves: RHEL-142053       Resolves: RHEL-142049       Resolves: RHEL-142045       Resolves: RHEL-142041       Resolves: RHEL-142037       Resolves: RHEL-142033       Resolves: RHEL-142029       Resolves: RHEL-142008       Resolves: RHEL-142025       Resolves: RHEL-142021

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 version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 4b824428-fb93-11f0-b194-8447094a420f advisory.

    The OpenSSL project reports:

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

    - Fix CVE-2025-11187 CVE-2025-15467 CVE-2025-15468 CVE-2025-15469       CVE-2025-66199 CVE-2025-68160 CVE-2025-69418 CVE-2025-69419 CVE-2025-69420       CVE-2025-69421 CVE-2026-22795 CVE-2026-22796       Resolves: RHEL-142062       Resolves: RHEL-141985       Resolves: RHEL-142053       Resolves: RHEL-142049       Resolves: RHEL-142045       Resolves: RHEL-142041       Resolves: RHEL-142037       Resolves: RHEL-142033       Resolves: RHEL-142029       Resolves: RHEL-142008       Resolves: RHEL-142025       Resolves: RHEL-142021
    - Fix CVE-2025-9230       Resolves: RHEL-115885

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

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

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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
322483	Tenable Identity Exposure < 3.93.5 Multiple Vulnerabilities (TNS-2026-16)	Nessus	Misc.	2026/6/24	2026/6/25	high
297055	AlmaLinux 10 : openssl (ALSA-2026:1472)	Nessus	Alma Linux Local Security Checks	2026/1/28	2026/4/30	high
297081	SUSE SLES15 Security Update : openssl-3 (SUSE-SU-2026:0311-1)	Nessus	SuSE Local Security Checks	2026/1/29	2026/4/30	high
297089	SUSE SLES15 Security Update : openssl-3 (SUSE-SU-2026:0310-1)	Nessus	SuSE Local Security Checks	2026/1/29	2026/4/30	high
297240	Photon OS 5.0: Openssl PHSA-2026-5.0-0747	Nessus	PhotonOS Local Security Checks	2026/1/30	2026/4/30	high
297823	Photon OS 4.0: Openssl PHSA-2026-4.0-0952	Nessus	PhotonOS Local Security Checks	2026/2/4	2026/4/30	high
298229	SUSE SLES16 Security Update : openssl-3 (SUSE-SU-2026:20223-1)	Nessus	SuSE Local Security Checks	2026/2/6	2026/2/6	high
300570	IBM MQ 9.1 < 9.1.0.34 LTS / 9.2 < 9.2.0.41 LTS / 9.3 < 9.3.0.37 LTS / 9.3 < 9.4.5.0 CD / 9.4 < 9.4.0.20 LTS (7262259)	Nessus	Misc.	2026/3/4	2026/3/4	high
328839	Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-7.6)	Nessus	Misc.	2026/7/21	2026/7/27	critical
328966	Tenable Security Center Multiple Vulnerabilities (TNS-2026-19)	Nessus	Misc.	2026/7/22	2026/7/23	critical
319344	EulerOS Virtualization 2.10.0 : openssl (EulerOS-SA-2026-2058)	Nessus	Huawei Local Security Checks	2026/6/6	2026/6/6	high
297022	RHEL 9 : openssl (RHSA-2026:1473)	Nessus	Red Hat Local Security Checks	2026/1/28	2026/4/30	high
297075	SUSE SLED15: libopenssl-3-devel / libopenssl-3-fips-provider / etc (SUSE-SU-2026:0309-1)	Nessus	SuSE Local Security Checks	2026/1/29	2026/6/26	high
297105	Oracle Linux 10 : openssl (ELSA-2026-1472)	Nessus	Oracle Linux Local Security Checks	2026/1/29	2026/4/30	high
297209	FreeBSD : OpenSSL -- Multiple vulnerabilities (4b824428-fb93-11f0-b194-8447094a420f)	Nessus	FreeBSD Local Security Checks	2026/1/30	2026/2/3	high
297341	Oracle Linux 10 : openssl (ELSA-2026-50081)	Nessus	Oracle Linux Local Security Checks	2026/1/31	2026/4/30	high
297451	Fedora 43 : openssl (2026-5f7d0a5656)	Nessus	Fedora Local Security Checks	2026/1/31	2026/4/30	high

检测

插件搜索

high

high

high

high

high

high

high

high

critical

critical

high

high

high

high

high

high

high