The CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS-STREAM8:CLSA-2026:1789995979 advisory.

  - When decompressing crafted zip files using the bzip/LZMA/Zstandard compressions, Python could use an     attacker-controlled size to pre-allocate memory, possibly resulting in memory exhaustion. (CVE-2026-15310)

  - The stringprep module didn't process characters from RFC 3454 tables B.2 or B.3 correctly: the latest     Unicode codepoint attributes were used instead of the specified Unicode 3.2.0. This behavior would cause     mismatches when processing domain names using IDNA 2003 (the idna codec) and the in_table_b2() function     of the stringprep module. This only affects domain names containing characters that were not previously     registered or had their Unicode attributes such as case-folding behavior updated since Unicode 3.2.0.
    (CVE-2026-17084)

  - When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member     from the archive. In this case, the filter function is run twice: once for the extracted member, and once     with name set to the location of the link. For one of the calls, the return value was ignored. Instead,     the member should be skipped if either call returns None. (CVE-2026-87910)

  - bz2.BZ2Decompressor objects could be reused after a decompression error. If an application caught the     resulting OSError and retried with the same decompressor, crafted input could cause the decompressor to     resume from an invalid internal state and perform out-of-bounds writes to a stack buffer. This could crash     the process when processing untrusted data. (CVE-2026-9669)

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.

  - When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member     from the archive. In this case, the filter function is run twice: once for the extracted member, and once     with name set to the location of the link. For one of the calls, the return value was ignored. Instead,     the member should be skipped if either call returns None. (CVE-2026-87910)

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3230 advisory.

    When decompressing crafted zip files using the bzip/LZMA/Zstandard

    compressions, Python could use an attacker-controlled size to

    pre-allocate memory, possibly resulting in memory exhaustion. (CVE-2026-15310)

    The HTTPPasswordMgr class in the urllib.request module, along with its subclasses     HTTPPasswordMgrWithDefaultRealm and HTTPPasswordMgrWithPriorAuth, did not take the URL scheme into account     when matching stored credentials against a requested URL. Credentials added for an https:// URL were also     used for requests to the same host over http://, so an attacker able to redirect or downgrade a client to     plain HTTP (for example, via an HTTPS-to-HTTP redirect or an on-path position) could capture credentials     in cleartext. Credentials added for http:// URLs could likewise be sent over https://.

    Credential matching is now scoped by URL scheme. Credentials registered with a URL that includes a scheme     are only used for requests with the same scheme. Credentials registered with a bare authority (such as     example.com or example.com:8080) continue to match any scheme, preserving compatibility with existing     code, including proxy authentication.

    Users who cannot upgrade immediately can mitigate by ensuring that applications never make plain http://     requests to hosts for which credentials are registered, for example by not following redirects to http://     URLs. (CVE-2026-15806)

    The stringprep module didn't process characters from RFC 3454 tablesB.2 or B.3 correctly: the latest     Unicode codepoint attributes were usedinstead of the specified Unicode 3.2.0. This behavior would     causemismatches when processing domain names using IDNA 2003 (the idnacodec) and the in_table_b2()     function of the stringprep module. Thisonly affects domain names containing characters that were not     previouslyregistered or had their Unicode attributes such as case-foldingbehavior updated since Unicode     3.2.0. (CVE-2026-17084)

    A remote, unauthenticated TLS client can make a server crash or callthrough a freed pointer if its     sni_callback assigns a different context toSSLSocket.context (the documented way to select a certificate     per servername) and nothing else keeps the original ssl.SSLContext alive. Typicalcases are servers that     create an SSLContext per connection or replace itwhile connections are open; servers that wrap their     listening socket withit are not affected.

    Mitigation: keep a reference to every SSLContext that sets sni_callback forthe lifetime of the server. TLS     clients are not affected. (CVE-2026-19445)

    ssl.SSLContext.wrap_bio() didn't require the server_hostname argumentto not be None if     ssl.SSLContext.check_hostname was set. Due to amissing parameter check in SSLObject, if the     server_hostname argumentisn't supplied then hostname verification would be silently skipped.

    This defect could lead to programs where certificate hostname verification*appeared* to be succeeding with     SSLContext.check_hostname = True and noValueError being raised due to misconfiguration.

    If the program passes a server_hostname value that isn't an empty stringor None to any of these APIs then     certificate hostname verificationproceeds as expected and the program is not affected by this     vulnerability.

    Mitigating this vulnerability doesn't require updating Python or applyingthe patch. To mitigate, pass a     valid non-None and non-emptyserver_hostname value to SSLContext.wrap_bio(),asyncio.create_connection(), or     asyncio.loop.start_tls() andcertificate hostname verification will proceed as expected. Upgrading tothe     latest version of Python or applying the patch only changes thebehavior from silently skipping hostname     verification to raising aValueError, similar to SSLContext.wrap_socket(), when server_hostnameisn't     supplied. (CVE-2026-19553)

    The tarfile module's tar and dataextraction filters created directories outside the destination formembers     whose name leaves the destination and returns to it, such as ../evil/../dest/sub/file. The containment     check used the resolved path, but intermediate directories were created from the name as given.

    Onlyempty directories are created outside the destination. Member contentsare still extracted inside it.
    To return to the destination the member'sname must contain the destination directory's own final     component, soextraction into a secure randomised directory is not affected.

    This affects POSIX platforms only. On Windows, .. components are collapsed before the path reaches the     filesystem, so the directories outside the destination are never created. (CVE-2026-19672)

    In CPython 3.13 and earlier, the tarfile module's data and tar extraction filters are vulnerable to     crafted archives containing a hard link to a symbolic link. Such archives may cause extraction to modify     the permissions or modification time of a file outside the destination directory, or expose the contents     of that file within the extracted tree. (CVE-2026-82049)

    When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member     from the archive. In this case, the filter function is run twice: once for the extracted member, and once     with name set to the location of the link. For one of the calls, the return value was ignored. Instead,     the member should be skipped if either call returns None. (CVE-2026-87910)

Tenable has extracted the preceding description block directly from the tested product 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 AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1790155146 advisory.

  - To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the     VPATH variable is defined at build time and used to locate certain landmarks - specifically,     Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python     assumes it is running in a source tree and generates a different default sys.path. This code remains in     release builds, so that release-ready builds can be built in-tree. On Windows, since builds are written to     'PCbuild/', the value of VPATH is set to '..\..', which results in a landmark of     '..\..\Modules\setup.local'. This path is outside the install directory of Python, and may have different     permissions, potentially allowing a low-privilege user to create the landmark and an alternative `Lib`     folder that will be discovered by an otherwise restricted install. Such a setup occurs with the legacy     default install location for all users (in the now superseded EXE installer), due to how Windows allows     all users to create folders in the root directory of their OS drive. Our recommended mitigation on Windows     is to migrate away from the legacy installer and use the new [Python install     manager](https://www.python.org/downloads/latest/pymanager/) to install for the current user. Installs     where the directory two levels above the Python installation directory have equivalent permissions are     unaffected (in general, a per-user install cannot be modified at all by other users, removing any     escalation of privilege risk, and could be directly modified by a privileged user, making the potential     tampering irrelevant). Alternative mitigations might include preemptively creating and restricting access     to a `Modules` directory. Be aware that only 3.13 and 3.14 will receive updated legacy installers -     earlier fixes are only provided as sources. Platforms other than Windows allow VPATH to be overridden, but     as they don't usually use a separated directory in the build for binaries, are unlikely to have a landmark     reference outside of the install directory. The landmark detection involving VPATH is a fallback for when     a more specific landmark - .\pybuilddir.txt - is absent, and was included for compatibility. Future     releases of Python will no longer include the fallback, and so builds will need to generate or preserve     the pybuilddir.txt file in order to work in-tree. This landmark file has been generated on Windows since     3.11, and on other platforms for longer. (CVE-2026-12003)

  - The stringprep module didn't process characters from RFC 3454 tables B.2 or B.3 correctly: the latest     Unicode codepoint attributes were used instead of the specified Unicode 3.2.0. This behavior would cause     mismatches when processing domain names using IDNA 2003 (the idna codec) and the in_table_b2() function     of the stringprep module. This only affects domain names containing characters that were not previously     registered or had their Unicode attributes such as case-folding behavior updated since Unicode 3.2.0.
    (CVE-2026-17084)

  - The tarfile module's tar and data extraction filters created directories outside the destination for     members whose name leaves the destination and returns to it, such as ../evil/../dest/sub/file. The     containment check used the resolved path, but intermediate directories were created from the name as     given. Only empty directories are created outside the destination. Member contents are still extracted     inside it. To return to the destination the member's name must contain the destination directory's own     final component, so extraction into a secure randomised directory is not affected. This affects POSIX     platforms only. On Windows, .. components are collapsed before the path reaches the filesystem, so the     directories outside the destination are never created. (CVE-2026-19672)

  - When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member     from the archive. In this case, the filter function is run twice: once for the extracted member, and once     with name set to the location of the link. For one of the calls, the return value was ignored. Instead,     the member should be skipped if either call returns None. (CVE-2026-87910)

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 TuxCare ALMALINUX9.6:CLSA-2026:1789993238 advisory.

  - When decompressing crafted zip files using the bzip/LZMA/Zstandard compressions, Python could use an     attacker-controlled size to pre-allocate memory, possibly resulting in memory exhaustion. (CVE-2026-15310)

  - The stringprep module didn't process characters from RFC 3454 tables B.2 or B.3 correctly: the latest     Unicode codepoint attributes were used instead of the specified Unicode 3.2.0. This behavior would cause     mismatches when processing domain names using IDNA 2003 (the idna codec) and the in_table_b2() function     of the stringprep module. This only affects domain names containing characters that were not previously     registered or had their Unicode attributes such as case-folding behavior updated since Unicode 3.2.0.
    (CVE-2026-17084)

  - When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member     from the archive. In this case, the filter function is run twice: once for the extracted member, and once     with name set to the location of the link. For one of the calls, the return value was ignored. Instead,     the member should be skipped if either call returns None. (CVE-2026-87910)

  - bz2.BZ2Decompressor objects could be reused after a decompression error. If an application caught the     resulting OSError and retried with the same decompressor, crafted input could cause the decompressor to     resume from an invalid internal state and perform out-of-bounds writes to a stack buffer. This could crash     the process when processing untrusted data. (CVE-2026-9669)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
352045	CentOS Linux 8 [TuxCare] Security Update: platform-python / platform-python-debug / platform-python-devel / etc Multiple Vulnerabilities (CENTOS-STREAM8:CLSA-2026:1789995979)	Nessus	CentOS Local Security Checks	2026/9/30	2026/9/30	high
345123	Linux Distros Unpatched Vulnerability : CVE-2026-87910	Nessus	Misc.	2026/9/12	2026/11/2	medium
371884	Amazon Linux 2023 : python3.12, python3.12-devel, python3.12-idle (ALAS2023-2026-3230)	Nessus	Amazon Linux Local Security Checks	2026/10/25	2026/10/30	critical
351910	AlmaLinux 9.2 [TuxCare] Security Update: python3.11 / python3.11-debug / python3.11-devel / python3.11-idle / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1790155146)	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/9/30	medium
352362	Rocky Linux 9.6 [TuxCare] Security Update: python-unversioned-command / python3 / python3-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1789993238)	Nessus	Rocky Linux Local Security Checks	2026/9/30	2026/9/30	high

检测

插件搜索

high

medium

critical

medium

high