CVE-2026-7168 is a credential leak (CWE-294) in libcurl 7.12.0 to 8.19.0: when an application uses Digest authentication with one HTTP proxy and then switches the same handle to a second proxy, libcurl sends the first proxy's Proxy-Authorization header to the second. NVD scores it 5.3; curl 8.20.0 fixes it.
Vulnerability summary
CVSS base score
5.3
Medium severity
EPSS score (FIRST)
0.5%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2026-7168 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| libcurl | cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:* | 7.12.0 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.12.0 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; wrynose (8.19.0) applies CVE-2026-7168.patch; scarthgap (8.7.1) and whinlatter (8.17.0) have no patch or CVE_STATUS entry (read 2026-11-18) |
| OpenWrt packages feed: 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); 8.23.0 on all three on 2026-11-18 |
What does this mean for affected devices?
The curl project's advisory describes it this way: using libcurl for a transfer over one HTTP proxy (proxyA) with Digest authentication and then changing the proxy host to proxyB for a second transfer on the same handle "makes libcurl wrongly pass on the Proxy-Authorization: header field meant for proxyA, to proxyB." A malicious proxyB could use that header to impersonate the client towards proxyA; the advisory notes that nothing in the request tells proxyB the name or address of proxyA, which limits the damage (curl advisory). curl rates it Medium, files it under CWE-294 (Authentication Bypass by Capture-replay), and says the curl command line tool is not affected. The advisory was also posted to oss-security on 2026-04-29.
NVD's Primary score is CVSS v3.1 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), the same as CISA's ADP entry, with CWE-294 from both NVD and curl as CNA. NVD's CPE configuration covers haxx:curl from 7.12.0 up to, but excluding, 8.20.0, and the record dates from 2026-05-13 (NVD).
When is a device's libcurl exposed to CVE-2026-7168?
Only when the firmware's own code drives libcurl through two different HTTP proxies with Digest proxy authentication on one reused easy handle. All three conditions sit in the application: proxy support in the build, Digest set through CURLOPT_PROXYAUTH, and a change of CURLOPT_PROXY between transfers without a fresh handle. Proxy support is on by default in OpenWrt's curl package configuration, and the scarthgap curl recipe enables both digest-auth and proxy in its default PACKAGECONFIG, so the code is usually present; whether it is reachable depends on whether the device ever switches between authenticated proxies, which a firmware update client behind one fixed corporate proxy does not do. Our libcurl vulnerabilities in embedded firmware guide groups it with CVE-2026-6253, CVE-2026-6429 and CVE-2026-8927 as proxy credential leaks that disappear when proxy support is compiled out.
Which firmware build systems carry the fix?
Buildroot's security bump to libcurl 8.20.0 on 2026-05-02 lists CVE-2026-7168 among the fixed CVEs, and OpenEmbedded-Core master's upgrade from 8.19.0 to 8.20.0 on 2026-06-04 names it too. On 2026-11-18 the wrynose recipe (curl 8.19.0) applies CVE-2026-7168.patch, but the scarthgap recipe (curl 8.7.1) and the whinlatter recipe (curl 8.17.0) carry neither a patch nor a CVE_STATUS entry for it, so images built from those branches keep the flaw unless the product layer adds the fix.
OpenWrt skipped 8.20.0: the packages feed moved 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.
How do you fix or mitigate it?
curl's recommendations, in order: upgrade curl and libcurl to 8.20.0, apply the patch to the local version and rebuild, or avoid reusing handles when changing proxies. The last option is a small code change in most device agents: create a new easy handle, or reset it, before pointing it at a different proxy. The same release fixed CVE-2026-5545, the Negotiate connection-reuse flaw, so one upgrade covers both. For other curl flaws on this site, see CVE-2023-38546 and CVE-2024-6197.
CVE-2026-7168 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00471, the 41st percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).
Evidence
- curl advisory 2026-04-29: after a Digest-authenticated transfer over proxyA, changing the proxy host to proxyB on the same handle makes libcurl pass the Proxy-Authorization header meant for proxyA to proxyB; an evil proxyB could impersonate the client to proxyA; nothing reveals proxyA's name or address; does not affect the curl tool; severity Medium; CWE-294; affected 7.12.0 to 8.19.0; not affected >= 8.20.0, >= 8.16.1 in 8.16.X, >= 8.14.2 in 8.14.X; recommendations: upgrade to 8.20.0, patch, avoid reusing handles when changing proxies; reported 2026-04-27 by Muhamad Arga Reksapati. — curl project
- NVD Primary CVSS 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N; CISA-ADP 5.3 same vector; CWE-294 from NVD and curl (CNA); CPE haxx:curl 7.12.0 to <8.20.0; published 2026-05-13. — NVD
- oss-security post 2026-04-29: [ADVISORY] curl: CVE-2026-7168: cross-proxy Digest auth state leak. — oss-security
- Buildroot commit 8940fae6 (2026-05-02) security bump to 8.20.0 fixes CVE-2026-7168; OE-core commit 492e9df5 (2026-06-04) upgrade 8.19.0 -> 8.20.0 lists CVE-2026-7168. — Buildroot / OpenEmbedded-Core
- wrynose curl_8.19.0.bb applies CVE-2026-7168.patch; scarthgap curl_8.7.1.bb and whinlatter curl_8.17.0.bb have no CVE-2026-7168 patch or CVE_STATUS; scarthgap default PACKAGECONFIG includes digest-auth and proxy. — OpenEmbedded-Core
- OpenWrt curl Config.in: LIBCURL_PROXY default y; packages feed moved 8.19.0 -> 8.21.0 on master 2026-07-04, openwrt-25.12 2026-09-10, openwrt-24.10 2026-09-22; 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.00471, percentile 0.41318, dataset 2026-11-17. — FIRST EPSS

Related advisories
Sources
- NVD
- curl security advisory: CVE-2026-7168, cross-proxy Digest auth state leak
- curl advisory JSON metadata: CVE-2026-7168
- oss-security: curl CVE-2026-7168 advisory
- 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 package configuration
- CISA KEV
- FIRST EPSS
Frequently asked questions
Which curl versions are affected by CVE-2026-7168?
libcurl 7.12.0 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. The curl command line tool is not affected (per the curl advisory).
What does an application have to do to trigger CVE-2026-7168?
Run a transfer through one HTTP proxy with Digest proxy authentication, then change the proxy host on the same libcurl handle for a second transfer. libcurl then sends the first proxy's Proxy-Authorization header to the second proxy (per the curl advisory).
Is the Yocto scarthgap curl recipe patched for CVE-2026-7168?
No. On 2026-11-18 the scarthgap curl 8.7.1 recipe in OpenEmbedded-Core has no CVE-2026-7168 patch and no CVE_STATUS entry for it; the wrynose recipe applies CVE-2026-7168.patch and master builds a fixed curl release.
Is CVE-2026-7168 in the CISA KEV catalog?
No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00471, the 41st percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?