The remote RockyLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2025:10148 advisory.

    * cpython: Tarfile extracts filtered members when errorlevel=0 (CVE-2025-4435)

    * cpython: Bypass extraction filter to modify file metadata outside extraction directory (CVE-2024-12718)

    * cpython: Extraction filter bypass for linking outside extraction directory (CVE-2025-4330)

    * python: cpython: Arbitrary writes via tarfile realpath overflow (CVE-2025-4517)

    * cpython: python: Bypassing extraction filter to create symlinks to arbitrary targets outside extraction     directory (CVE-2025-4138)

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 Tencent Linux installed on the remote TencentOS Server 3 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2025:0559 advisory.

    Package updates are available for TencentOS Server 3 that fix the following vulnerabilities:

    CVE-2024-12718:
    Allows modifying some file metadata (e.g. last modified) with filter=dataor file permissions (chmod)     with filter=tarof files outside the extraction directory.
    You are affected by this vulnerability if using the tarfilemodule to extract untrusted tar archives     using TarFile.extractall()or TarFile.extract()using the filter=parameter with a value of dataor     tar. See the tarfile  extraction filters documentation     https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information. Only     Python versions 3.12 or later are affected by these vulnerabilities, earlier versions don't include the     extraction filter feature.

    Note that for Python 3.14 or later the default value of filter=changed from no filtering to data, so     if you are relying on this new default behavior then your usage is also affected.

    Note that none of these vulnerabilities significantly affect the installation of source distributions     which are tar archives as source distributions already allow arbitrary code execution during the build     process. However when evaluating source distributions it's important to avoid installing source     distributions with suspicious links.

    CVE-2025-4138:
    Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination     directory, and the modification of some file metadata.


    You are affected by this vulnerability if using the tarfilemodule to extract untrusted tar archives     using TarFile.extractall()or TarFile.extract()using the filter=parameter with a value of dataor     tar. See the tarfile  extraction filters documentation     https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information.

    Note that for Python 3.14 or later the default value of filter=changed from no filtering to data, so     if you are relying on this new default behavior then your usage is also affected.

    Note that none of these vulnerabilities significantly affect the installation of source distributions     which are tar archives as source distributions already allow arbitrary code execution during the build     process. However when evaluating source distributions it's important to avoid installing source     distributions with suspicious links.

    CVE-2025-4330:
    Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination     directory, and the modification of some file metadata.


    You are affected by this vulnerability if using the tarfilemodule to extract untrusted tar archives     using TarFile.extractall()or TarFile.extract()using the filter=parameter with a value of dataor     tar. See the tarfile  extraction filters documentation     https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information.

    Note that for Python 3.14 or later the default value of filter=changed from no filtering to data, so     if you are relying on this new default behavior then your usage is also affected.

    Note that none of these vulnerabilities significantly affect the installation of source distributions     which are tar archives as source distributions already allow arbitrary code execution during the build     process. However when evaluating source distributions it's important to avoid installing source     distributions with suspicious links.

    CVE-2025-4435:
    When using a TarFile.errorlevel = 0and extracting with a filter the documented behavior is that any     filtered members would be skipped and not extracted. However the actual behavior of TarFile.errorlevel =     0in affected versions is that the member would still be extracted and not skipped.

    CVE-2025-4517:
    Allows arbitrary filesystem writes outside the extraction directory during extraction with filter=data.


    You are affected by this vulnerability if using the tarfilemodule to extract untrusted tar archives     using TarFile.extractall()or TarFile.extract()using the filter=parameter with a value of dataor     tar. See the tarfile  extraction filters documentation     https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information.

    Note that for Python 3.14 or later the default value of filter=changed from no filtering to data, so     if you are relying on this new default behavior then your usage is also affected.

    Note that none of these vulnerabilities significantly affect the installation of source distributions     which are tar archives as source distributions already allow arbitrary code execution during the build     process. However when evaluating source distributions it's important to avoid installing source     distributions with suspicious links.

Tenable has extracted the preceding description block directly from the Tencent 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 Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2025:0502 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2025-6069:
    The html.parser.HTMLParser class had worse-case quadratic complexity when processing certain crafted     malformed inputs potentially leading to amplified denial-of-service.

    CVE-2025-4517:
    Allows arbitrary filesystem writes outside the extraction directory during extraction with filter=data.


    You are affected by this vulnerability if using the tarfilemodule to extract untrusted tar archives     using TarFile.extractall()or TarFile.extract()using the filter=parameter with a value of dataor     tar. See the tarfile  extraction filters documentation     https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information.

    Note that for Python 3.14 or later the default value of filter=changed from no filtering to `data,     so if you are relying on this new default behavior then your usage is also affected.

    Note that none of these vulnerabilities significantly affect the installation of source distributions     which are tar archives as source distributions already allow arbitrary code execution during the build     process. However when evaluating source distributions it's important to avoid installing source     distributions with suspicious links.

    CVE-2025-4435:
    When using a TarFile.errorlevel = 0and extracting with a filter the documented behavior is that any     filtered members would be skipped and not extracted. However the actual behavior of TarFile.errorlevel =     0in affected versions is that the member would still be extracted and not skipped.

    CVE-2025-4330:
    Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination     directory, and the modification of some file metadata.


    You are affected by this vulnerability if using the tarfilemodule to extract untrusted tar archives     using TarFile.extractall()or TarFile.extract()using the filter=parameter with a value of dataor     tar. See the tarfile  extraction filters documentation     https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information.

    Note that for Python 3.14 or later the default value of filter=changed from no filtering to `data,     so if you are relying on this new default behavior then your usage is also affected.

    Note that none of these vulnerabilities significantly affect the installation of source distributions     which are tar archives as source distributions already allow arbitrary code execution during the build     process. However when evaluating source distributions it's important to avoid installing source     distributions with suspicious links.

    CVE-2025-4138:
    Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination     directory, and the modification of some file metadata.


    You are affected by this vulnerability if using the tarfilemodule to extract untrusted tar archives     using TarFile.extractall()or TarFile.extract()using the filter=parameter with a value of dataor     tar. See the tarfile  extraction filters documentation     https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information.

    Note that for Python 3.14 or later the default value of filter=changed from no filtering to `data,     so if you are relying on this new default behavior then your usage is also affected.

    Note that none of these vulnerabilities significantly affect the installation of source distributions     which are tar archives as source distributions already allow arbitrary code execution during the build     process. However when evaluating source distributions it's important to avoid installing source     distributions with suspicious links.

    CVE-2024-12718:
    Allows modifying some file metadata (e.g. last modified) with filter=dataor file permissions (chmod)     with filter=tarof files outside the extraction directory.
    You are affected by this vulnerability if using the tarfilemodule to extract untrusted tar archives     using TarFile.extractall()or TarFile.extract()using the filter=parameter with a value of dataor     tar. See the tarfile  extraction filters documentation     https://docs.python.org/3/library/tarfile.html#tarfile-extraction-filter for more information. Only     Python versions 3.12 or later are affected by these vulnerabilities, earlier versions don't include the     extraction filter feature.

    Note that for Python 3.14 or later the default value of filter=changed from no filtering to `data,     so if you are relying on this new default behavior then your usage is also affected.

    Note that none of these vulnerabilities significantly affect the installation of source distributions     which are tar archives as source distributions already allow arbitrary code execution during the build     process. However when evaluating source distributions it's important to avoid installing source     distributions with suspicious links.

Tenable has extracted the preceding description block directly from the Tencent 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 RockyLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2025:23530 advisory.

    * python: Invalid value for OpenSSL API may cause Buffer over-read when NPN is used (CVE-2024-5642)

    * python: Virtual environment (venv) activation scripts don't quote paths (CVE-2024-9287)

    * python: Improper validation of IPv6 and IPvFuture addresses (CVE-2024-11168)

    * python: cpython: URL parser allowed square brackets in domain names (CVE-2025-0938)

    * cpython: python: CPython DecodeError Handling Vulnerability (CVE-2025-4516)

    * cpython: Tarfile extracts filtered members when errorlevel=0 (CVE-2025-4435)

    * cpython: python: Extraction filter bypass for linking outside extraction directory (CVE-2025-4330)

    * python: cpython: Arbitrary writes via tarfile realpath overflow (CVE-2025-4517)

    * cpython: python: Bypassing extraction filter to create symlinks to arbitrary targets outside extraction     directory (CVE-2025-4138)

    * cpython: Python HTMLParser quadratic complexity (CVE-2025-6069)

    * cpython: python: Python zipfile End of Central Directory (EOCD) Locator record offset not checked     (CVE-2025-8291)

    * python: Quadratic complexity in os.path.expandvars() with user-controlled template (CVE-2025-6075)

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.

An update of the python3 package has been released.

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

  - LZ4 before 1.9.2 has a heap-based buffer overflow in LZ4_write32 (related to LZ4_compress_destSize),     affecting applications that call LZ4_compress_fast with a large input. (This issue can also lead to data     corruption.) NOTE: the vendor states only a few specific / uncommon usages of the API are at risk.
    (CVE-2019-17543)

  - setuptools is a package that allows users to download, build, install, upgrade, and uninstall Python     packages. A path traversal vulnerability in `PackageIndex` is present in setuptools prior to version     78.1.1. An attacker would be allowed to write files to arbitrary locations on the filesystem with the     permissions of the process running the Python code, which could escalate to remote code execution     depending on the context. Version 78.1.1 fixes the issue. (CVE-2025-47273)

  - A use-after-free vulnerability was found in libxml2. This issue occurs when parsing XPath elements under     certain circumstances when the XML schematron has the <sch:name path=.../> schema elements. This flaw     allows a malicious actor to craft a malicious XML document used as input for libxml, resulting in the     program's crash using libxml or other possible undefined behaviors. (CVE-2025-49794)

  - A vulnerability was found in libxml2. Processing certain sch:name elements from the input XML file can     trigger a memory corruption issue. This flaw allows an attacker to craft a malicious XML input file that     can lead libxml to crash, resulting in a denial of service or other possible undefined behavior due to     sensitive data being corrupted in memory. (CVE-2025-49796)

  - A flaw was found in libxml2's xmlBuildQName function, where integer overflows in buffer size calculations     can lead to a stack-based buffer overflow. This issue can result in memory corruption or a denial of     service when processing crafted input. (CVE-2025-6021)

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

  - 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)

  - 1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise     made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set 3.
    The same cookie name is set - but with only a slash as path (`path=/`). Since this site is not secure,     the cookie *should* be ignored. 4. A bug in the path comparison logic makes curl read outside a heap     buffer boundary The bug either causes a crash or it potentially makes the comparison come to the wrong     conclusion and lets the clear-text site override the contents of the secure cookie, contrary to     expectations and depending on the memory contents immediately following the single-byte allocation that     holds the path. The presumed and correct behavior would be to plainly ignore the second set of the cookie     since it was already set as secure on a secure host so overriding it on an insecure host should not be     okay. (CVE-2025-9086)

  - net-snmp is a SNMP application library, tools and daemon. Prior to versions 5.9.5 and 5.10.pre2, a     specially crafted packet to an net-snmp snmptrapd daemon can cause a buffer overflow and the daemon to     crash. This issue has been patched in versions 5.9.5 and 5.10.pre2. (CVE-2025-68615)

  - The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname     verification of the peer certificate, even when the verifyHostName     https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName     configuration attribute or the log4j2.sslVerifyHostName     https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property     is set to true. This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic     under the following conditions: * The attacker is able to intercept or redirect network traffic between     the client and the log receiver. * The attacker can present a server certificate issued by a certification     authority trusted by the Socket Appender's configured trust store (or by the default Java trust store if     no custom trust store is configured). Users are advised to upgrade to Apache Log4j Core version 2.25.3,     which addresses this issue. As an alternative mitigation, the Socket Appender may be configured to use a     private or restricted trust root to limit the set of trusted certificates. (CVE-2025-68161)

  - Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can     trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which     leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which     can have various consequences including a Denial of Service or Execution of attacker-supplied code.
    Although the consequences of a successful exploit of this vulnerability could be severe, the probability     that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in     CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to     our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue,     as the CMS implementation is outside the OpenSSL FIPS module boundary. (CVE-2025-9230)

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

  - 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)

  - LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable     Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, an out-of-bounds read     vulnerability exists in png_image_read_composite when processing palette images with     PNG_FLAG_OPTIMIZE_ALPHA enabled. The palette compositing code in png_init_read_transformations incorrectly     applies background compositing during premultiplication, violating the invariant component  alpha  257     required by the simplified PNG API. This issue has been patched in version 1.6.51. (CVE-2025-64720)

  - LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable     Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, there is a heap buffer overflow     vulnerability in the libpng simplified API function png_image_finish_read when processing 16-bit     interlaced PNGs with 8-bit output format. Attacker-crafted interlaced PNG files cause heap writes beyond     allocated buffer bounds. This issue has been patched in version 1.6.51. (CVE-2025-65018)

  - Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of     Oracle Java SE (component: RMI). Supported versions that are affected are Oracle Java SE: 8u471,     8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9;
    Oracle GraalVM Enterprise Edition: 21.3.16. Difficult to exploit vulnerability allows unauthenticated     attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK,     Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized     update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM     Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Java SE,     Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be     exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the     APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web     Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from     the internet) and rely on the Java sandbox for security. (CVE-2026-21925)

  - Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of     Oracle Java SE (component: Networking). Supported versions that are affected are Oracle Java SE: 8u471,     8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9;
    Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated     attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK,     Oracle GraalVM Enterprise Edition. Successful attacks require human interaction from a person other than     the attacker and while the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM     Enterprise Edition, attacks may significantly impact additional products (scope change). Successful     attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle     Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized     read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition     accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g.,     through a web service which supplies data to the APIs. This vulnerability also applies to Java     deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets,     that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox     for security. (CVE-2026-21933)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
266534	RockyLinux 9 : python3.11 (RLSA-2025:10148)	Nessus	Rocky Linux Local Security Checks	2025/10/4	2026/2/24	critical
276070	TencentOS Server 3: python3 (TSSA-2025:0559)	Nessus	Tencent Local Security Checks	2025/11/20	2026/3/11	critical
276174	TencentOS Server 4: python3.11 (TSSA-2025:0502)	Nessus	Tencent Local Security Checks	2025/11/20	2026/3/11	critical
279075	RockyLinux 8 : python39:3.9 (RLSA-2025:23530)	Nessus	Rocky Linux Local Security Checks	2025/12/18	2026/2/24	medium
332463	Photon OS 5.0: Python3 PHSA-2025-5.0-91-0554	Nessus	PhotonOS Local Security Checks	2026/8/5	2026/8/5	critical
258029	Nutanix AHV : Multiple Vulnerabilities (NXSA-AHV-10.0.1.3)	Nessus	Misc.	2025/8/27	2026/8/13	high
299670	Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-7.5.0.6)	Nessus	Misc.	2026/2/20	2026/9/15	medium
299799	Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-7.3.1.5)	Nessus	Misc.	2026/2/23	2026/4/7	medium

检测

插件搜索

critical

critical

critical

medium

critical

high

medium

medium