CVE-2026-5545 is a connection-reuse flaw (CWE-305) in libcurl and the curl tool, versions 7.10.6 to 8.19.0: after a request authenticated with HTTP Negotiate, a later request to the same host with different credentials can reuse the connection still logged in as the first user. NVD scores it 6.5; curl 8.20.0 fixes it.
Vulnerability summary
CVSS base score
6.5
Medium severity
EPSS score (FIRST)
0.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2026-5545 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| curl / libcurl | cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:* | 7.10.6 to 8.19.0 (curl advisory); fixed in 8.20.0. curl also lists 8.14.2 (8.14.x) and 8.16.1 (8.16.x) as not affected; NVD's CPE range is 7.10.6 up to, excluding, 8.20.0 |
| OpenEmbedded-Core curl recipe | cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:* | master upgraded to 8.20.0 on 2026-06-04; scarthgap (8.7.1) and wrynose (8.19.0) apply CVE-2026-5545.patch; whinlatter (8.17.0) has no patch (read 2026-11-18) |
| OpenWrt packages feed: curl / libcurl | cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:* | 8.19.0 replaced by 8.21.0 (master 2026-07-04, openwrt-25.12 2026-09-10, openwrt-24.10 2026-09-22); GSS-API only with the Kerberos option, off by default |
What does this mean for affected devices?
The curl project's advisory says 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." An application that authenticates to a server with Negotiate as user1 and then, while that connection is still alive, asks for a request to the same server as user2 gets the old connection, which is still authenticated as user1 (curl advisory). The project rates it Medium, files it under CWE-305 (Authentication Bypass by Primary Weakness), and says the flaw also affects the curl command line tool.
NVD's Primary score is CVSS v3.1 6.5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N), the same score and vector as CISA's ADP entry; NVD maps it to CWE-613 (Insufficient Session Expiration), while curl as CNA gives CWE-305. NVD's CPE configuration covers haxx:curl from 7.10.6 up to, but excluding, 8.20.0. curl published the advisory on 2026-04-29 together with release 8.20.0; the NVD record dates from 2026-05-13 (NVD).
When is a device's libcurl exposed to CVE-2026-5545?
Only when its libcurl can do Negotiate at all and the application uses it. The CURLOPT_HTTPAUTH documentation says Negotiate needs libcurl built "with a suitable GSS-API library or SSPI on Windows", and the bug then needs two authenticated requests with different credentials to the same host over a live connection. A provisioning agent that always logs in to its update server as one device account does not hit it; a gateway that proxies requests for several users to one Kerberos-protected server might.
Embedded Linux defaults often leave GSS-API out. OpenWrt's curl package gained a Kerberos option, which passes --with-gssapi, only on 2026-09-07, and the option is off by default (OpenWrt commit 00ea941), so a stock OpenWrt libcurl has no Negotiate support. In OpenEmbedded-Core the krb5 PACKAGECONFIG maps to --with-gssapi and is absent from the default list in the scarthgap curl recipe. Check the Features: line of curl -V, or the build configuration, for GSS-API before treating a version match as a finding; our libcurl vulnerabilities in embedded firmware guide lists it with CVE-2026-1965 and CVE-2026-19931 as Negotiate connection-reuse issues that drop out when Negotiate is compiled out.
Which firmware build systems carry the fix?
Buildroot applied a security bump to libcurl 8.20.0 on 2026-05-02 that lists CVE-2026-5545 among the fixed CVEs. OpenEmbedded-Core master upgraded curl from 8.19.0 to 8.20.0 on 2026-06-04 with the same CVE in its commit message. The stable branches backport instead: on 2026-11-18 the scarthgap recipe (curl 8.7.1) and the wrynose recipe (curl 8.19.0) both apply CVE-2026-5545.patch, while the whinlatter recipe (curl 8.17.0) has no patch for it.
OpenWrt never packaged 8.20.0. Its packages feed went from 8.19.0 to curl 8.21.0 on master on 2026-07-04, on openwrt-25.12 on 2026-09-10 and on openwrt-24.10 on 2026-09-22, and all three branches build 8.23.0 on 2026-11-18. The curl advisory also names 8.14.2 and 8.16.1 as not affected on the 8.14.x and 8.16.x branches; neither is in the public curl.se download directory, and NVD's CPE range still matches them, so expect a scanner hit on those builds.
How do you fix or mitigate it?
curl's recommendations, in order: upgrade curl and libcurl to 8.20.0, apply the patch and rebuild, or stop using HTTP Negotiate in the application. Where neither is possible, the advisory says applications can turn off connection reuse with CURLOPT_FRESH_CONNECT, CURLOPT_MAXCONNECTS or, with the multi API, CURLMOPT_MAX_HOST_CONNECTIONS. The same release also fixed CVE-2026-7168, a Digest proxy credential leak, so one upgrade covers both. For older curl flaws with a firmware angle, see CVE-2023-38545 and CVE-2024-6197; the authentication bypass fix guide covers this class of bug in device code.
CVE-2026-5545 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00414, the 36th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).
Evidence
- curl advisory 2026-04-29: libcurl might reuse the wrong connection for an authenticated HTTP(S) request after a Negotiate-authenticated one to the same host; severity Medium; CWE-305; also affects the curl tool; affected 7.10.6 to 8.19.0; not affected >= 8.20.0, >= 8.16.1 in 8.16.X, >= 8.14.2 in 8.14.X; mitigations CURLOPT_FRESH_CONNECT, CURLOPT_MAXCONNECTS, CURLMOPT_MAX_HOST_CONNECTIONS; recommendations: upgrade to 8.20.0, apply patch, avoid HTTP Negotiate; reported 2026-04-01 by Quac Tran and Ngoc Hieu. — curl project
- NVD Primary CVSS 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N; CISA-ADP 6.5 same vector; NVD CWE-613, CNA (curl) CWE-305; CPE haxx:curl 7.10.6 to <8.20.0; published 2026-05-13. — NVD
- CURLAUTH_NEGOTIATE: You need to build libcurl with a suitable GSS-API library or SSPI on Windows for this to work. — curl documentation
- Buildroot commit 8940fae6 (2026-05-02) package/libcurl: security bump to version 8.20.0, fixes CVE-2026-5545 and CVE-2026-7168 among others. — Buildroot
- OE-core commit 492e9df5 (2026-06-04) curl: upgrade 8.19.0 -> 8.20.0, CVE: CVE-2026-5545, CVE-2026-7168; scarthgap curl_8.7.1.bb and wrynose curl_8.19.0.bb apply CVE-2026-5545.patch; whinlatter curl_8.17.0.bb does not; krb5 PACKAGECONFIG = --with-gssapi, not in scarthgap default PACKAGECONFIG. — OpenEmbedded-Core
- OpenWrt packages: curl 8.19.0 -> 8.21.0 on master 2026-07-04 (21ad076), openwrt-25.12 2026-09-10, openwrt-24.10 2026-09-22; Kerberos option (--with-gssapi) added 2026-09-07, default n; all three branches at 8.23.0 on 2026-11-18. — OpenWrt packages feed
- Not in the CISA KEV catalog, version 2026.11.17, checked 2026-11-18. — CISA KEV
- EPSS 0.00414, percentile 0.36216, dataset 2026-11-17. — FIRST EPSS

Related advisories
Sources
- NVD
- curl security advisory: CVE-2026-5545, wrong reuse of HTTP Negotiate connection
- curl advisory JSON metadata: CVE-2026-5545
- curl documentation: CURLOPT_HTTPAUTH
- Buildroot: package/libcurl security bump to version 8.20.0
- OpenEmbedded-Core: curl upgrade 8.19.0 to 8.20.0
- OpenEmbedded-Core scarthgap curl 8.7.1 recipe
- OpenEmbedded-Core wrynose curl 8.19.0 recipe
- OpenEmbedded-Core whinlatter curl 8.17.0 recipe
- OpenWrt packages: curl update to 8.21.0
- OpenWrt packages: curl Kerberos support
- CISA KEV
- FIRST EPSS
Frequently asked questions
Which curl versions are affected by CVE-2026-5545?
curl and libcurl 7.10.6 to 8.19.0. curl 8.20.0 fixes it, and the curl advisory also lists 8.14.2 and 8.16.1 as not affected on their branches. NVD's CPE range is 7.10.6 up to, but excluding, 8.20.0 (per the curl advisory and NVD).
Does CVE-2026-5545 affect a libcurl built without GSS-API?
The bug needs a Negotiate-authenticated connection, and curl's CURLOPT_HTTPAUTH documentation says Negotiate needs libcurl built with a GSS-API library or SSPI on Windows. OpenWrt's curl package passes --with-gssapi only when its Kerberos option, off by default, is selected.
How can a device mitigate CVE-2026-5545 without upgrading?
Apply the upstream patch and rebuild, stop using HTTP Negotiate, or disable connection reuse with CURLOPT_FRESH_CONNECT, CURLOPT_MAXCONNECTS or CURLMOPT_MAX_HOST_CONNECTIONS, as the curl advisory lists.
Is CVE-2026-5545 in the CISA KEV catalog?
No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00414, the 36th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?