Successfully using libcurl to do a transfer over a specific HTTP proxy
(proxyA) with Digest authentication and then changing the proxy host to
a second one (proxyB) for a second transfer, reusing the same handle, makes
libcurl wrongly pass on the Proxy-Authorization: header field meant for
proxyA, to proxyB.
CVE-2026-7168
Score 5.3 from GitHub Security Advisory published 2026-05-13. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 55(Attend)EG Risk 55/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 39%
- KEV
- Not listed
Published
May 13, 2026
Last Modified
June 23, 2026
Advisory Details (4)
Auto-updated Jun 17, 2026oss-security - [ADVISORY] curl: CVE-2026-7168: cross-proxy Digest auth state leak
http://www.openwall.com/lists/oss-security/2026/04/29/14curl - cross-proxy Digest auth state leak - CVE-2026-7168
https://curl.se/docs/CVE-2026-7168.htmlVendor Advisories for CVE-2026-7168(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libcurl4t64 (8.5.0-2ubuntu10.11) @ noble | 2026-08-23 | ubuntu |
| ubuntu | libcurl4t64 (8.18.0-1ubuntu2.1) @ resolute | 2026-08-23 | ubuntu |
| redhat | curl-main-8.20.0-2.hum1 | 2026-05-19 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(6 across 6 ecosystems)
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | — | 8.20.0-r0 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | — | 8.20.0-r0 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | 7.74.0-1.3 ... 8.9.1-2~bpo12+1 (219 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | 7.88.1-10 ... 7.88.1-10+deb12u9 (18 versions) | 7.88.1-10+deb12u15 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | 8.14.1-2, 8.14.1-2+deb13u1, 8.14.1-2+deb13u2, 8.14.1-2+deb13u2~bpo13+1, 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | 8.14.1-2 ... 8.20.0~rc3-1+exp1 (49 versions) | 8.20.0-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 12× in last 7d / 75× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 204 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 14:18 UTCEPSS rescore
- 2026-08-23 17:57 UTCEG score recompute
- 2026-08-23 17:57 UTCVendor advisory
- 2026-08-23 17:57 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 21:33 UTCEG score recompute
- 2026-08-20 21:33 UTCVendor advisory
- 2026-08-20 21:33 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 10:44 UTCEG score recompute
- 2026-08-17 10:44 UTCVendor advisory
- 2026-08-17 10:44 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:08 UTCEG score recompute
- 2026-08-16 04:08 UTCVendor advisory
- 2026-08-16 04:08 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 01:31 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-14 02:36 UTCEG score recompute
- 2026-08-14 02:36 UTCVendor advisory
- 2026-08-14 02:36 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 15:54 UTCEG score recompute
- 2026-08-12 15:54 UTCVendor advisory
- 2026-08-12 15:54 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 05:59 UTCEG score recompute
- 2026-08-11 05:59 UTCVendor advisory
- 2026-08-11 05:59 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 04:50 UTCEG score recompute
- 2026-08-10 04:50 UTCVendor advisory
- 2026-08-10 04:50 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 03:42 UTCEG score recompute
- 2026-08-09 03:42 UTCVendor advisory
- 2026-08-09 03:42 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 02:33 UTCEG score recompute
- 2026-08-08 02:33 UTCVendor advisory
- 2026-08-08 02:33 UTCGHSA enrichment
- 2026-08-07 01:25 UTCEG score recompute
- 2026-08-07 01:25 UTCVendor advisory
- 2026-08-07 01:25 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 21:43 UTCEG score recompute
- 2026-08-05 21:43 UTCVendor advisory
- 2026-08-05 21:43 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 23:35 UTCEG score recompute
- 2026-08-03 23:35 UTCVendor advisory
- 2026-08-03 23:35 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 22:24 UTCEG score recompute
- 2026-08-02 22:24 UTCVendor advisory
- 2026-08-02 22:24 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 21:14 UTCEG score recompute
- 2026-08-01 21:14 UTCVendor advisory
- 2026-08-01 21:14 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 23:23 UTCOSV refresh
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
- CVE-2001-0011EG 10.0EPSS p94HIGH
- CVE-2001-0013EG 10.0EPSS p95HIGH
Same CWE
10 shownCWE-294
- CVE-2021-22640NVD 7.5EG 9.8CRITICAL
- CVE-2022-29334EG 9.8CRITICAL
- CVE-2022-22806EG 9.8EPSS p96CRITICAL
- CVE-2020-35551EG 9.8CRITICAL
- CVE-2018-19025EG 9.8CRITICAL
- CVE-2018-17932EG 9.8CRITICAL
- CVE-2019-18226EG 9.8CRITICAL
- CVE-2018-7790EG 9.8CRITICAL
- CVE-2017-3191EG 9.8EPSS p99CRITICAL
- CVE-2017-6034EG 9.8EPSS p92CRITICAL
Frequently asked(5)
What is CVE-2026-7168?
When was CVE-2026-7168 disclosed?
Is CVE-2026-7168 actively exploited?
What is the CVSS score of CVE-2026-7168?
How do I remediate CVE-2026-7168?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-7168
Is Your Infrastructure Affected by CVE-2026-7168?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.