Skip to content
OpenAdvisories
High ELSA-2026-55439 4 CVEs

Important: curl security update (Oracle Linux 9)

Published Aug 17, 2026 · Updated Aug 17, 2026

Summary

[7.76.1-40.el9_8.5]
- fix missing %patch macros for Patch46 and Patch47

[7.76.1-40.el9_8.4]
- fix HTTP Negotiate connection reuse auth bypass (CVE-2026-1965)
- fix OAuth2 bearer token leak via redirect and netrc (CVE-2026-3783)
- tests: disable flaky test 1206 on x86_64 (FTP PORT timeout under valgrind)

[7.76.1-40.3]
- tests: disable flaky tests 3000, 3001 on i686 (stunnel startup race)

[7.76.1-40.1]
- fix SSH host key mismatch on type difference (CVE-2026-9547)
- fix TLS/STARTTLS connection reuse vulnerability (CVE-2026-8286)

Fixed packages 5

ReleasePackageFixed in
Oracle Linux · 9 curl 0:7.76.1-40.el9_8.5
Oracle Linux · 9 curl-minimal 0:7.76.1-40.el9_8.5
Oracle Linux · 9 libcurl 0:7.76.1-40.el9_8.5
Oracle Linux · 9 libcurl-devel 0:7.76.1-40.el9_8.5
Oracle Linux · 9 libcurl-minimal 0:7.76.1-40.el9_8.5

Vulnerabilities 4

  • High 8.1

    wrong STARTTLS connection reuse

    A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.

  • High 7.4

    SSH improper host validation

    When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match…

  • Medium 6.5

    bad reuse of HTTP Negotiate connection

    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 …

  • Medium 5.3

    token leak with redirect and netrc

    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 informa…