The version of AHV installed on the remote host is prior to 10.3.1.12. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AHV-10.3.1.12 advisory.

  - pyOpenSSL is a Python wrapper around the OpenSSL library. Starting in version 22.0.0 and prior to version     26.0.0, if a user provided callback to `set_cookie_generate_callback` returned a cookie value greater than     256 bytes, pyOpenSSL would overflow an OpenSSL provided buffer. Starting in version 26.0.0, cookie values     that are too long are now rejected. (CVE-2026-27459)

  - Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was     previously freed in some situations Impact summary: A use after free can have a range of potential     consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only     applications that directly call the SSL_free_buffers function are affected by this issue. Applications     that do not call this function are not vulnerable. Our investigations indicate that this function is     rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer     used when processing an incoming record from the network. The call is only expected to succeed if the     buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even     when still in use. The first scenario occurs where a record header has been received from the network and     processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers     will succeed even though a record has only been partially processed and the buffer is still in use. The     second scenario occurs where a full record containing application data has been received and processed by     OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed     even though the buffer is still in use. While these scenarios could occur accidentally during normal     operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware     of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this     issue. (CVE-2024-4741)

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

  - Rsync versions before 3.4.3 contain a time-of-check to time-of-use (TOCTOU) race condition in daemon file     handling that allows attackers to redirect file writes outside intended directories by replacing parent     directory components with symbolic links. Attackers with write access to a module path can exploit this     race condition to create or overwrite arbitrary files, potentially modifying sensitive system files and     achieving privilege escalation when the daemon runs with elevated privileges. This vulnerability can only     be triggered if the chroot setting is false. (CVE-2026-29518)

  - Rsync version 3.4.2 and prior contain an integer overflow vulnerability in the compressed-token decoder     where a 32-bit signed counter is not checked for overflow, allowing a malicious sender to trigger an     overflow that causes the receiver process to read and return data from outside the intended buffer bounds.
    Attackers can exploit this vulnerability to disclose process memory contents including environment     variables, passwords, heap and stack data, and library memory pointers, significantly reducing ASLR     effectiveness and facilitating further exploitation. (CVE-2026-43618)

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

  - A flaw was found in gnutls. Servers configured with RSA-PSK (RivestShamirAdleman  Pre-Shared Key)     wrongfully matched usernames containing a NUL character with truncated usernames. A remote attacker could     exploit this by sending a specially crafted username, leading to an authentication bypass. This     vulnerability allows an attacker to gain unauthorized access by circumventing the authentication process.
    (CVE-2026-42010)

  - Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send     contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer     might contain sensitive data from the previous execution of the application process which leads to     sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success     and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA     encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave     the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced. If     applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key     without first validating that key, then this may cause stale or uninitialized contents of the caller-     provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext. As a workaround     calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will     mitigate the issue. The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.
    (CVE-2026-31790)

  - Calling the scanf family of functions with a %mc (malloc'd character match) in the GNU C Library version     2.7 to version 2.43 with a format width specifier with an explicit width greater than 1024 could result in     a one byte heap buffer overflow. (CVE-2026-5450)

  - An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7. Formatting error     messages with xmllint --htmlout can result in a buffer over-read in xmlHTMLPrintFileContext in xmllint.c.
    (CVE-2024-34459)

  - A use-after-free vulnerability was found in libxslt while parsing xsl nodes that may lead to the     dereference of expired pointers and application crash. (CVE-2025-10911)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
335151	Nutanix AHV : Multiple Vulnerabilities (NXSA-AHV-10.3.1.12)	Nessus	Misc.	2026/8/13	2026/8/13	critical
341615	Nutanix AHV : Multiple Vulnerabilities (NXSA-AHV-11.2.0.2)	Nessus	Misc.	2026/8/31	2026/8/31	high

检测

插件搜索

critical

high