CVE-2026-7168

MEDIUMNVD 5.35.3—

5.3

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.

CVSS v3: 5.3
EG Score: 5.3(high)
EPSS: 23.2%
KEV: Not listed

Published

May 13, 2026

Last Modified

May 14, 2026

References (5)

2499f714-1537-4658-8207-48ae4bb9eae9https://curl.se/docs/CVE-2026-7168.html
2499f714-1537-4658-8207-48ae4bb9eae9https://curl.se/docs/CVE-2026-7168.json
2499f714-1537-4658-8207-48ae4bb9eae9https://hackerone.com/reports/3697719
af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2026/04/29/14
134c704f-9b21-4f2e-91b3-4a467353bcc0https://hackerone.com/reports/3697719

Vendor Advisories for CVE-2026-7168(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

CVE-2026-7168
Microsoft Security Response Center (MSRC)
cross-proxy Digest auth state leak

Frequently asked(5)

What is CVE-2026-7168?

CVE-2026-7168 is a medium vulnerability published on May 13, 2026. 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,…

When was CVE-2026-7168 disclosed?

CVE-2026-7168 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on May 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-7168 actively exploited?

CVE-2026-7168 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-7168?

CVE-2026-7168 has a CVSS v3 base score of 5.3 (NVD).

How do I remediate CVE-2026-7168?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7168, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-7168

Explore →

Is Your Infrastructure Affected by CVE-2026-7168?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2026-7168

📅 Published

🔄 Last Modified

🔗 References (5)

📣 Vendor Advisories for CVE-2026-7168(1)

❓ Frequently asked(5)