An update of the curl package has been released.

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

  - Tenable Identity Exposure contains multiple unauthenticated API endpoints under /w/api/* that expose     sensitive application configuration data including cleartext LDAP credentials, SAML configuration, user     accounts, and directory settings to unauthenticated remote attackers. Affected responses are served with     Cache-Control: public headers and without Vary: Cookie, allowing reverse proxies and CDNs to cache and     serve sensitive data to unauthenticated users even after authentication is applied. (CVE-2026-13007)

  - Inconsistent interpretation of http requests ('http request/response smuggling') in ASP.NET Core allows     an authorized attacker to bypass a security feature over a network. (CVE-2025-55315)

  - Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer     overflow on 32 bit platforms. A heap buffer overflow may lead to a crash or possibly an attacker     controlled code execution or other undefined behavior. (CVE-2026-31789)

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 might in some circumstances reuse the wrong connection when asked to     do an authenticated HTTP(S) request after a Negotiate-authenticated one, when     both use the same host.

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

    An application that first uses Negotiate authentication to a server with     `user1:password1` and then does another operation to the same server asking     for any authentication method but for `user2:password2` (while the previous     connection is still alive) - the second request gets confused and wrongly     reuses the same connection and sends the new request over that connection     thinking it uses a mix of user1's and user2's credentials when it is in fact     still using the connection authenticated for user1...(CVE-2026-5545)

    curl might erroneously pass on credentials for a first proxy to a second     proxy.

    This can happen when the following conditions are true:

    1. curl is setup to use specific different proxies for different URL schemes     2. the first proxy needs credentials     3. the second proxy uses no credentials     4. while using the first proxy (using say `http://`), curl is asked to follow        a redirect to a URL using another scheme (say `https://`), accessed using a        second, different, proxy(CVE-2026-6253)

    libcurl might in some circumstances reuse the wrong connection for SMB(S)     transfers.

    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 criteria must be met. Due to a logical     error in the code, a network transfer operation that was requested by an     application could wrongfully reuse an existing SMB connection to the same     server that was using a different 'share' than the new subsequent transfer     should.

    This could in unlucky situations lead to the download of the wrong file or the     upload of a file to the wrong place. When this happens, the same credentials     are used and the server name is the same.(CVE-2026-5773)

    Using libcurl, when a custom `Host:` header is first set for an HTTP request     and a second request is subsequently done using the same *easy handle* but     without the custom `Host:` header set, the second request would use stale     information and pass on cookies meant for the first host in the second     request. Leak them.(CVE-2026-6276)

    A vulnerability exists where a connection requiring TLS incorrectly reuses an     existing unencrypted connection from the same connection pool. If an initial     transfer is made in clear-text (via IMAP, SMTP, or POP3), a subsequent request     to that same host bypasses the TLS requirement and instead transmit data     unencrypted.(CVE-2026-4873)

    When asked to both use a `.netrc` file for credentials and to follow HTTP     redirects, libcurl could leak the password used for the first host to the     followed-to host under certain circumstances.(CVE-2026-6429)

    Successfully using libcurl to do a transfer over a specific HTTP proxy     (`proxyA`) with **Digest** authentication and then changing the proxy host to     a second one (`proxyB`) for a second transfer, reusing the same handle, makes     libcurl wrongly pass on the `Proxy-Authorization:` header field meant for     `proxyA`, to `proxyB`.(CVE-2026-7168)

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.

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

    libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S)     request after a Negotiate-authenticated one, when both use the same host.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 criteria must 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.An application that first uses Negotiate authentication to a     server with `user1:password1` and then does another operation to the same server asking for any     authentication method but for `user2:password2` (while the previous connection is still alive) - the     second request gets confused and wrongly reuses the same connection and sends the new request over that     connection thinking it uses a mix of user1's and user2's credentials when it is in fact still using the     connection authenticated for user1...(CVE-2026-5545)

    curl might erroneously pass on credentials for a first proxy to a second proxy. This can happen when the     following conditions are true: 1. curl is setup to use specific different proxies for different URL     schemes 2. the first proxy needs credentials 3. the second proxy uses no credentials 4. while using the     first proxy (using say `http://`), curl is asked to follow a redirect to a URL using another scheme (say     `https://`), accessed using a second, different, proxy(CVE-2026-6253)

    libcurl might in some circumstances reuse the wrong connection for SMB(S) transfers. 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 criteria must be met. Due to a logical error in the code, a network     transfer operation that was requested by an application could wrongfully reuse an existing SMB connection     to the same server that was using a different 'share' than the new subsequent transfer should. This could     in unlucky situations lead to the download of the wrong file or the upload of a file to the wrong place.
    When this happens, the same credentials are used and the server name is the same.(CVE-2026-5773)

    Using libcurl, when a custom `Host:` header is first set for an HTTP request and a second request is     subsequently done using the same *easy handle* but without the custom `Host:` header set, the second     request would use stale information and pass on cookies meant for the first host in the second request.
    Leak them.(CVE-2026-6276)

    A vulnerability exists where a connection requiring TLS incorrectly reuses an existing unencrypted     connection from the same connection pool. If an initial transfer is made in clear-text (via IMAP, SMTP, or     POP3), a subsequent request to that same host bypasses the TLS requirement and instead transmit data     unencrypted.
    (CVE-2026-4873)

    When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, libcurl could leak     the password used for the first host to the followed-to host under certain circumstances.(CVE-2026-6429)

    Successfully using libcurl to do a transfer over a specific HTTP proxy (`proxyA`) with **Digest**     authentication and then changing the proxy host to a second one (`proxyB`) for a second transfer, reusing     the same handle, makes libcurl wrongly pass on the `Proxy-Authorization:` header field meant for `proxyA`,     to `proxyB`.(CVE-2026-7168)

Tenable has extracted the preceding description block directly from the EulerOS Virtualization 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 remote Ubuntu 22.04 LTS / 24.04 LTS / 25.10 / 26.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-8227-1 advisory.

    It was discovered that curl incorrectly reused non-TLS connections when TLS was required in some STARTTLS     configurations. A remote attacker could possibly use this issue to obtain sensitive information.
    (CVE-2026-4873)

    It was discovered that curl incorrectly reused certain HTTP Negotiate connections. A remote attacker could     possibly use this issue to obtain sensitive information. (CVE-2026-5545)

    It was discovered that curl incorrectly reused certain SMB connections. A remote attacker could possibly     use this issue to obtain sensitive information. (CVE-2026-5773)

    It was discovered that curl could leak proxy credentials when handling redirects in some configurations. A     remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-6253)

    It was discovered that curl could leak cookies because of stale custom cookie host handling in some     requests. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-6276)

    It was discovered that curl could leak .netrc credentials when reusing proxy connections in some     situations. A remote attacker could possibly use this issue to obtain sensitive information.
    (CVE-2026-6429)

    It was discovered that curl could leak Digest authentication state when switching proxies in some     situations. A remote attacker could possibly use this issue to obtain sensitive information.
    (CVE-2026-7168)

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.

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

    When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling,     to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead     wrongly consider the response as fine.  If the returned status reports another error than 'revoked' (like     for example 'unauthorized') it is not treated as a bad certficate.(CVE-2024-8096)

    When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache     entry, making it end sooner or later than otherwise intended. This affects curl using applications that     enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like     `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS     cache either needs to have been populated manually or there needs to have been previous HTTPS accesses     done as the cache needs to have entries for the domains involved to trigger this problem.) When     `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's     expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The     result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different     period of time than what was asked for by the origin server. If `example.com` for example stops supporting     HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set)     timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently     switch back to insecure HTTP earlier than otherwise intended.(CVE-2024-9681)

    When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, curl could leak the     password used for the first host to the followed-to host under certain circumstances.This flaw only     manifests itself if the netrc file has an entry that matches the redirect target hostname but the entry     either omits just the password or omits both login and password.(CVE-2024-11053)

    When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the     `CURLOPT_ACCEPT_ENCODING` option,**using zlib 1.2.0.3 or older**, an attacker-controlled integer overflow     would make libcurl perform a buffer overflow.(CVE-2025-0725)

    When asked to use a `.netrc` file for credentials **and** to follow HTTP redirects, curl could leak the     password used for the first host to the followed-to host under certain circumstances.This flaw only     manifests itself if the netrc file has a `default` entry that omits both login and password. A rare     circumstance.(CVE-2025-0167)

    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 just a slash as path (`path='/'`).Since this site is not secure,     the cookie *should* just 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)

    curl's code for managing SSH connections when SFTP was done using the wolfSSH powered backend was flawed     and missed host verification mechanisms.This prevents curl from detecting MITM attackers and     more.(CVE-2025-10966)

    When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could     still mistakenly accept connecting to hosts *not present* in the specified file if they were added as     recognized in the libssh *global* known_hosts file.(CVE-2025-15079)

    When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl,changing TLS options in one thread     would inadvertently change them globally and therefore possibly also affect other concurrently setup     transfers.Disabling certificate verification for a specific transfer could unintentionally disable the     feature for other threads as well.(CVE-2025-14017)

    When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol     redirect to a second URL that uses an IMAP, LDAP,POP3 or SMTP scheme, curl might wrongly pass on the     bearer token to the new target host.(CVE-2025-14524)

    When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl     would wrongly still ask and authenticate using a locally running SSH agent.(CVE-2025-15224)

    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)

    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)

    When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, libcurl could leak     the password used for the first host to the followed-to host under certain circumstances.(CVE-2026-6429)

    Successfully using libcurl to do a transfer over a specific HTTP proxy (`proxyA`) with **Digest**     authentication and then changing the proxy host to a second one (`proxyB`) for a second transfer, reusing     the same handle, makes libcurl wrongly pass on the `Proxy-Authorization:` header field meant for `proxyA`,     to `proxyB`.(CVE-2026-7168)

    libcurl might in some circumstances reuse the wrong connection for SMB(S)transfers.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 criteria must be met. Due to a logical error in the code, a network     transfer operation that was requested by an application could wrongfully reuse an existing SMB connection     to the same server that was using a different 'share' than the new subsequent transfer should.This could     in unlucky situations lead to the download of the wrong file or the upload of a file to the wrong place.
    When this happens, the same credentials are used and the server name is the same.(CVE-2026-5773)

    libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S)     request after a Negotiate-authenticated one, when both use the same host.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 criteria must 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.An application that first uses Negotiate authentication to a server with     `user1:password1` and then does another operation to the same server asking for any authentication method     but for `user2:password2` (while the previous connection is still alive) - the second request gets     confused and wrongly reuses the same connection and sends the new request over that connection thinking it     uses a mix of user1's and user2's credentials when it is in fact still using the connection authenticated     for user1...(CVE-2026-5545)

    curl might erroneously pass on credentials for a first proxy to a second proxy.This can happen when the     following conditions are true:1. curl is setup to use specific different proxies for different URL schemes     2. the first proxy needs credentials 3. the second proxy uses no credentials 4. while using the first     proxy (using say `http://`), curl is asked to follow a redirect to a URL using another scheme (say     `https://`), accessed using a second, different, proxy(CVE-2026-6253)

    Using libcurl, when a custom `Host:` header is first set for an HTTP request and a second request is     subsequently done using the same *easy handle* but without the custom `Host:` header set, the second     request would use stale information and pass on cookies meant for the first host in the second request.
    Leak them.(CVE-2026-6276)

    A vulnerability exists where a connection requiring TLS incorrectly reuses an existing unencrypted     connection from the same connection pool. If an initial transfer is made in clear-text (via IMAP, SMTP, or     POP3), a subsequent request to that same host bypasses the TLS requirement and instead transmit data     unencrypted.(CVE-2026-4873)

Tenable has extracted the preceding description block directly from the EulerOS Virtualization 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 remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:3798-1 advisory.

    - CVE-2026-5545: wrong reuse of HTTP Negotiate connection (bsc#1262632).
    - CVE-2026-5773: wrong reuse of SMB connection (bsc#1262633).
    - 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).
    - CVE-2026-7168: cross-proxy Digest auth state leak (bsc#1263440).
    - CVE-2026-8926: password leak with netrc and user in URL (bsc#1268412).

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.

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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
313013	Photon OS 5.0: Curl PHSA-2026-5.0-0838	Nessus	PhotonOS Local Security Checks	2026/5/7	2026/5/14	high
322483	Tenable Identity Exposure < 3.93.5 Multiple Vulnerabilities (TNS-2026-16)	Nessus	Misc.	2026/6/24	2026/6/25	high
332924	EulerOS 2.0 SP13 : curl (EulerOS-SA-2026-3012)	Nessus	Huawei Local Security Checks	2026/8/6	2026/8/6	high
339272	EulerOS Virtualization 2.13.0 : curl (EulerOS-SA-2026-3209)	Nessus	Huawei Local Security Checks	2026/8/25	2026/8/25	high
312298	Ubuntu 22.04 LTS / 24.04 LTS / 25.10 / 26.04 LTS : curl vulnerabilities (USN-8227-1)	Nessus	Ubuntu Local Security Checks	2026/5/5	2026/5/14	high
348099	EulerOS Virtualization 2.11.0 : curl (EulerOS-SA-2026-3495)	Nessus	Huawei Local Security Checks	2026/9/18	2026/9/18	high
347185	EulerOS Virtualization 2.11.1 : curl (EulerOS-SA-2026-3408)	Nessus	Huawei Local Security Checks	2026/9/18	2026/9/18	high
341033	SUSE SLED15 / SLES15 Security Update : curl (SUSE-SU-2026:3798-1)	Nessus	SuSE Local Security Checks	2026/8/27	2026/8/29	high
315269	SUSE SLES15 Security Update : curl (SUSE-SU-2026:1940-1)	Nessus	SuSE Local Security Checks	2026/5/19	2026/5/19	medium

检测

插件搜索

high

high

high

high

high

high

high

high

medium