CVE-2026-7168
MEDIUMDescription
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.1 Score
EPSS — Exploit Prediction
EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.
Weakness Type (CWE)
Affected Products
| Vendor | Product |
|---|---|
| haxx | curl |
References
Frequently Asked Questions
What is CVE-2026-7168? +
How severe is CVE-2026-7168? +
What products are affected by CVE-2026-7168? +
How do I check if I'm vulnerable to CVE-2026-7168? +
Related Vulnerabilities
SMB forced authentication vulnerability in versions prior to 2025.35.000 of Sage 200 Spain. This vulnerability allows an authenticated attacker with …
A weakness identified in OpenText Advanced Authentication where a Malicious browser plugin can record and replay the user authentication process …
Transmitted data is logged between the device and the backend service. An attacker could use these logs to perform a …
Use of fixed learning codes, one code to lock the car and the other code to unlock it, the Key …
Use of fixed learning codes, one code to lock the car and the other code to unlock it, in the …
Azure Bastion Elevation of Privilege Vulnerability