Alpine: curl: security update to 8.14.1-r3

high Tenable Cloud Security Plugin ID 476153

Description

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

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

- When using `CURLOPT_PINNEDPUBLICKEY` option with libcurl or `--pinnedpubkey` with the curl tool, curl
should check the public key of the server certificate to verify the peer. This check was skipped in a
certain condition that would then make curl allow the connection without performing the proper check, thus
not noticing a possible impostor. To skip this check, the connection had to be done with QUIC with ngtcp2
built to use GnuTLS and the user had to explicitly disable the standard certificate verification.
(CVE-2025-13034)

- 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 TLS related transfers with reused easy or multi handles and altering the
`CURLSSLOPT_NO_PARTIALCHAIN` option, libcurl could accidentally reuse a CA store cached in memory for
which the partial chain option was reversed. Contrary to the user's wishes and expectations. This could
make libcurl find and accept a trust chain that it otherwise would not. (CVE-2025-14819)

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

Solution

Update the curl library and its related packages to version 8.14.1-r3 or later.

Plugin Details

Severity: High

ID: 476153

Version: Revision 1.1

Type: Local

Family: Alpine Linux Local Security Checks

Published: 10/18/2026

Updated: 10/18/2026

Supported Sensors: Agentless Assessment

Risk Information

VPR

Risk Factor: High

Score: 7.9

Percentile: 99.35

CVSS v2

Risk Factor: High

Base Score: 7.8

Temporal Score: 6.1

Vector: CVSS2#AV:N/AC:L/Au:N/C:C/I:N/A:N

CVSS Score Source: CVE-2026-5773

CVSS v3

Risk Factor: High

Base Score: 7.5

Temporal Score: 6.7

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Temporal Vector: CVSS:3.0/E:P/RL:O/RC:C

Vulnerability Information

Exploit Available: true

Exploit Ease: Exploits are available

Vulnerability Publication Date: 1/8/2026

Reference Information

CVE: CVE-2025-13034, CVE-2025-14524, CVE-2025-14819, CVE-2026-1965, CVE-2026-3783, CVE-2026-3784, CVE-2026-3805, CVE-2026-4873, CVE-2026-5545, CVE-2026-5773, CVE-2026-6253, CVE-2026-6276, CVE-2026-6429, CVE-2026-7168, CVE-2026-8286, CVE-2026-8924, CVE-2026-8927, CVE-2026-92392

IAVA: 2026-A-0005-S, 2026-A-0237-S, 2026-A-0397-S, 2026-A-0627-S

Detections

Analytics

Alpine: curl: security update to 8.14.1-r3

high Tenable Cloud Security Plugin ID 476153

Description

Solution

See Also

Plugin Details

Risk Information

VPR

CVSS v2

CVSS v3

Vulnerability Information

Reference Information