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:1717-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 :

    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)

    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)

    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.

An update of the curl package has been released.

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

    A vulnerability, which was classified as problematic, has been found in cURL up to 8.19.0 (Network Utility     Software). Affected by this issue is some unknown functionality of the component SMB Connection Handler.
    Upgrading to version 8.20.0 eliminates this vulnerability.(CVE-2026-5773)

    A vulnerability has been found in cURL up to 8.19.0 (Network Utility Software) and classified as     problematic. This vulnerability affects an unknown code of the component Cookie Handler. Upgrading to     version 8.20.0 eliminates this vulnerability.(CVE-2026-6276)

    A vulnerability was found in cURL up to 8.19.0 (Network Utility Software). It has been classified as     problematic. Affected is some unknown processing of the component Cross-Proxy Digest Auth Handler.
    Upgrading to version 8.20.0 eliminates this vulnerability.(CVE-2026-7168)

    A vulnerability, which was classified as problematic, was found in cURL up to 8.19.0 (Network Utility     Software). This affects an unknown part of the component Redirect-to Proxy Handler. Upgrading to version     8.20.0 eliminates this vulnerability.(CVE-2026-6253)

    VUL-0: CVE-2026-6429: curl: netrc credential leak with reused proxy connection(CVE-2026-6429)

    VUL-0: CVE-2026-5545: curl: wrong reuse of HTTP Negotiate connection(CVE-2026-5545)

    VUL-0: CVE-2026-4873: curl: connection reuse ignores TLS requirement(CVE-2026-4873)

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

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

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

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

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

  - A flaw in curl's cookie parsing logic allows a malicious HTTP server to set super cookies that bypass     the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl     subsequently scopes and transmits to unrelated third-party domains. (CVE-2026-8924)

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.

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

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

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

ID	名前	製品	ファミリー	公開日	更新日	深刻度
313680	SUSE SLED15 / SLES15 Security Update : curl (SUSE-SU-2026:1717-1)	Nessus	SuSE Local Security Checks	2026/5/10	2026/5/14	medium
326141	EulerOS 2.0 SP12 : curl (EulerOS-SA-2026-2523)	Nessus	Huawei Local Security Checks	2026/7/10	2026/7/10	high
332662	Photon OS 5.0: Curl PHSA-2026-5.0-91-0838	Nessus	PhotonOS Local Security Checks	2026/8/5	2026/8/5	high
332789	EulerOS 2.0 SP15 : curl (EulerOS-SA-2026-2879)	Nessus	Huawei Local Security Checks	2026/8/6	2026/8/6	high
332939	EulerOS 2.0 SP13 : curl (EulerOS-SA-2026-2962)	Nessus	Huawei Local Security Checks	2026/8/6	2026/8/6	high
353059	AlmaLinux 9.6 [TuxCare] Security Update: curl / curl-minimal / libcurl / libcurl-devel / libcurl-minimal Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1785564870)	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/9/30	critical
310994	Linux Distros Unpatched Vulnerability : CVE-2026-4873	Nessus	Misc.	2026/4/29	2026/9/2	medium
322483	Tenable Identity Exposure < 3.93.5 Multiple Vulnerabilities (TNS-2026-16)	Nessus	Misc.	2026/6/24	2026/6/25	high
313013	Photon OS 5.0: Curl PHSA-2026-5.0-0838	Nessus	PhotonOS Local Security Checks	2026/5/7	2026/10/14	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

検出

プラグインの検索

medium

high

high

high

high

critical

medium

high

high

high

high