ALAS2-2026-4128


Amazon Linux 2 (EOS) Security Advisory: ALAS2-2026-4128
Advisory Released Date: 2026-11-19
Advisory Updated Date: 2026-11-19
Severity: Medium

Issue Overview:

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 libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a Set-Cookie header where the Domain attribute explicitly matches an origin host that is itself a public suffix (e.g., Domain=co.uk set by co.uk). Instead of coercing it into a strict host-only cookie, libcurl saves the cookie with wildcard domain scope (.co.uk). Consequently, the cookie is inappropriately included in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix (e.g., attacker.co.uk). (CVE-2026-82209)


Affected Packages:

curl


Note:

This advisory is applicable to Amazon Linux 2 (AL2) Core repository. Visit this FAQ section for the difference between AL2 Core and AL2 Extras advisories.


Issue Correction:
Run yum update curl or yum update --advisory ALAS2-2026-4128 to update your system.

New Packages:
aarch64:
    curl-8.3.0-1.amzn2.0.15.aarch64
    libcurl-8.3.0-1.amzn2.0.15.aarch64
    libcurl-devel-8.3.0-1.amzn2.0.15.aarch64
    curl-debuginfo-8.3.0-1.amzn2.0.15.aarch64

i686:
    curl-8.3.0-1.amzn2.0.15.i686
    libcurl-8.3.0-1.amzn2.0.15.i686
    libcurl-devel-8.3.0-1.amzn2.0.15.i686
    curl-debuginfo-8.3.0-1.amzn2.0.15.i686

src:
    curl-8.3.0-1.amzn2.0.15.src

x86_64:
    curl-8.3.0-1.amzn2.0.15.x86_64
    libcurl-8.3.0-1.amzn2.0.15.x86_64
    libcurl-devel-8.3.0-1.amzn2.0.15.x86_64
    curl-debuginfo-8.3.0-1.amzn2.0.15.x86_64