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

It is, therefore, affected by a vulnerability as referenced in the ALAS2023-2026-1699 advisory.

    When doing a second SMB request to the same host again, curl would wrongly use a data pointer pointing     into already freed memory. (CVE-2026-3805)

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

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

The AlmaLinux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1773939685 advisory.

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

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

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

  - When doing a second SMB request to the same host again, curl would wrongly use a data pointer pointing     into already freed memory. (CVE-2026-3805)

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 doing a second SMB request to the same host again, curl would wrongly use a data pointer pointing     into already freed memory. (CVE-2026-3805)

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

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.

ID	名前	製品	ファミリー	公開日	更新日	深刻度
307436	Tenable Identity Exposure < 3.77.17 Multiple Vulnerabilities (TNS-2026-11)	Nessus	Misc.	2026/4/18	2026/4/20	high
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
315018	Amazon Linux 2023 : curl, curl-minimal, libcurl (ALAS2023-2026-1699)	Nessus	Amazon Linux Local Security Checks	2026/5/16	2026/5/16	high
361814	AlmaLinux 9.6 [TuxCare] Security Update: curl / curl-minimal / libcurl / libcurl-devel / libcurl-minimal Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1773939685)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	medium
301854	Linux Distros Unpatched Vulnerability : CVE-2026-3805	Nessus	Misc.	2026/3/11	2026/11/6	high
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

検出

プラグインの検索

high

medium

medium

high

medium

high

medium

medium