The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated     HTTP or HTTPS request. libcurl features a pool of recent connections so that subsequent requests can reuse     an existing connection to avoid overhead. When reusing a connection a range of criterion must first be     met. Due to a logical error in the code, a request that was issued by an application could wrongfully     reuse an existing connection to the same server that was authenticated using different credentials. One     underlying reason being that Negotiate sometimes authenticates *connections* and not *requests*, contrary     to how HTTP is designed to work. An application that allows Negotiate authentication to a server (that     responds wanting Negotiate) with `user1:password1` and then does another operation to the same server also     using Negotiate but with `user2:password2` (while the previous connection is still alive) - the second     request wrongly reused the same connection and since it then sees that the Negotiate negotiation is     already made, it just sends the request over that connection thinking it uses the user2 credentials when     it is in fact still using the connection authenticated for user1... The set of authentication methods to     use is set with `CURLOPT_HTTPAUTH`. Applications can disable libcurl's reuse of connections and thus     mitigate this problem, by using one of the following libcurl options to alter how connections are or are     not reused: `CURLOPT_FRESH_CONNECT`, `CURLOPT_MAXCONNECTS` and `CURLMOPT_MAX_HOST_CONNECTIONS` (if using     the curl_multi API). (CVE-2026-1965)

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

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

  - A flaw in Node.js's Permissions model allows attackers to bypass --allow-fs-read and --allow-fs-write     restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script     granted access only to the current directory can escape the allowed path and read sensitive files. This     breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential     system compromise. (CVE-2025-55130)

  - Improper validation of specified type of input in SQL Server allows an authorized attacker to elevate     privileges over a network. (CVE-2026-26115)

  - Improper access control in Curl allows an authorized attacker to elevate privileges over a network.
    (CVE-2026-21262)

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:1940-1 advisory.

    Security issues fixed:

    - CVE-2026-4873: connection reuse ignores TLS requirement (bsc#1262631).
    - CVE-2026-5545: wrong reuse of HTTP Negotiate connection (bsc#1262632).
    - CVE-2026-6253: proxy credentials leak over redirect-to proxy (bsc#1262635).
    - CVE-2026-6276: stale custom cookie host causes cookie leak (bsc#1262636).
    - CVE-2026-6429: netrc credential leak with reused proxy connection (bsc#1262638).

    Other updates and bugfixes:

    - sws: prevent 'connection monitor' to say disconnect twice (bsc#1259362).

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.

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

    libcurl can in some circumstances reuse the wrong connection when asked to do_x000D_     an Negotiate-authenticated HTTP or HTTPS request._x000D_
    _x000D_     libcurl features a pool of recent connections so that subsequent requests can_x000D_     reuse an existing connection to avoid overhead._x000D_
    _x000D_     When reusing a connection a range of criterion must first be met. Due to a_x000D_     logical error in the code, a request that was issued by an application could_x000D_     wrongfully reuse an existing connection to the same server that was_x000D_     authenticated using different credentials. One underlying reason being that_x000D_     Negotiate sometimes authenticates *connections* and not *requests*, contrary_x000D_     to how HTTP is designed to work._x000D_
    _x000D_     An application that allows Negotiate authentication to a server (that responds_x000D_     wanting Negotiate) with `user1:password1` and then does another operation to_x000D_     the same server also using Negotiate but with `user2:password2` (while the_x000D_     previous connection is still alive) - the second request wrongly reused the_x000D_     same connection and since it then sees that the Negotiate negotiation is_x000D_     already made, it just sends the request over that connection thinking it uses_x000D_     the user2 credentials when it is in fact still using the connection_x000D_     authenticated for user1..._x000D_
    _x000D_     The set of authentication methods to use is set with  `CURLOPT_HTTPAUTH`._x000D_
    _x000D_     Applications can disable libcurl's reuse of connections and thus mitigate this_x000D_     problem, by using one of the following libcurl options to alter how_x000D_     connections are or are not reused: `CURLOPT_FRESH_CONNECT`,_x000D_     `CURLOPT_MAXCONNECTS` and `CURLMOPT_MAX_HOST_CONNECTIONS` (if using the_x000D_     curl_multi API).(CVE-2026-1965)

    curl would wrongly reuse an existing HTTP proxy connection doing CONNECT to a_x000D_     server, even if the new request uses different credentials for the HTTP proxy._x000D_     The proper behavior is to create or use a separate connection.(CVE-2026-3784)

    When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer_x000D_     performs a redirect to a second URL, curl could leak that token to the second_x000D_     hostname under some circumstances._x000D_
    _x000D_     If the hostname that the first request is redirected to has information in the_x000D_     used .netrc file, with either of the `machine` or `default` keywords, curl_x000D_     would pass on the bearer token set for the first host also to the second one.(CVE-2026-3783)

Tenable has extracted the preceding description block directly from the EulerOS curl 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 1933737d-1d46-11f1-81da-8447094a420f advisory.

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

    Zhicheng Chen discovered that curl could incorrectly reuse the wrong connection for Negotiate-     authenticated HTTP or HTTPS requests. This could result in the use of credentials from a different     connection, contrary to expectations. (CVE-2026-1965)

    It was discovered that curl incorrectly leaked OAuth2 bearer tokens when following a redirect. This could     result in tokens being sent to the wrong host, contrary to expectations. (CVE-2026-3783)

    Muhamad Arga Reksapati discovered that curl incorrectly reused existing HTTP proxy connections even if the     request used different credentials. This could result in the use of incorrect credentials, contrary to     expectations. (CVE-2026-3784)

    Daniel Wade discovered that curl incorrectly handled certain memory operations when doing a second SMB     request to the same host. An attacker could use this issue to cause curl to crash, resulting in a denial     of service, or possibly execute arbitrary code. This issue only affected Ubuntu 25.10. (CVE-2026-3805)

    Yihang Zhou discovered that curl incorrectly reused .netrc file credentials when following redirects. This     could result in the use of credentials for a different host, contrary to expectations. This issue only     affected Ubuntu 22.04 LTS and Ubuntu 24.04 LTS. (CVE-2025-0167)

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

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

An update of the curl package has been released.

The remote Fedora 43 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-66db242036 advisory.

    - Fix bad reuse of HTTP Negotiate connection (CVE-2026-1965)
    - Fix token leak with redirect and netrc (CVE-2026-3783)
    - Fix wrong proxy connection reuse with credentials (CVE-2026-3784)
    - Fix use after free in SMB connection reuse (CVE-2026-3805)

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.

The remote Fedora 44 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-f13d888b0f advisory.

    - Fix bad reuse of HTTP Negotiate connection (CVE-2026-1965)
    - Fix token leak with redirect and netrc (CVE-2026-3783)
    - Fix wrong proxy connection reuse with credentials (CVE-2026-3784)
    - Fix use after free in SMB connection reuse (CVE-2026-3805)

    ----

    -  Fix `Could not find digest algorithm UNDEF (NID 0)`

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	名称	产品	系列	发布时间	最近更新时间	严重程度
301847	Linux Distros Unpatched Vulnerability : CVE-2026-1965	Nessus	Misc.	2026/3/11	2026/7/30	medium
307436	Tenable Identity Exposure < 3.77.17 Multiple Vulnerabilities (TNS-2026-11)	Nessus	Misc.	2026/4/18	2026/4/20	high
315269	SUSE SLES15 Security Update : curl (SUSE-SU-2026:1940-1)	Nessus	SuSE Local Security Checks	2026/5/19	2026/5/19	medium
320296	EulerOS 2.0 SP13 : curl (EulerOS-SA-2026-2283)	Nessus	Huawei Local Security Checks	2026/6/10	2026/6/10	medium
301882	FreeBSD : curl -- Multiple vulnerabilties (1933737d-1d46-11f1-81da-8447094a420f)	Nessus	FreeBSD Local Security Checks	2026/3/11	2026/5/8	medium
302211	Ubuntu 22.04 LTS / 24.04 LTS / 25.10 : curl vulnerabilities (USN-8084-1)	Nessus	Ubuntu Local Security Checks	2026/3/13	2026/5/8	medium
303001	Photon OS 4.0: Curl PHSA-2026-4.0-0977	Nessus	PhotonOS Local Security Checks	2026/3/19	2026/5/8	medium
307656	Fedora 43 : curl (2026-66db242036)	Nessus	Fedora Local Security Checks	2026/4/20	2026/5/8	medium
310432	Fedora 44 : curl (2026-f13d888b0f)	Nessus	Fedora Local Security Checks	2026/4/27	2026/5/8	medium

检测

插件搜索

medium

high

medium

medium

medium

medium

medium

medium

medium