CVE-2026-7168
Description
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`.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| debian | bookworm | affected | |
| debian | bullseye | affected | |
| debian | forky | fixed | 8.20.0-1 |
| debian | sid | fixed | 8.20.0-1 |
| debian | trixie | affected | |
| sles | affected | | |
| windows | affected | |
References
- https://curl.se/docs/CVE-2026-7168.html
- https://curl.se/docs/CVE-2026-7168.json
- https://hackerone.com/reports/3697719
- http://www.openwall.com/lists/oss-security/2026/04/29/14
- https://security-tracker.debian.org/tracker/CVE-2026-7168
- https://www.suse.com/security/cve/CVE-2026-7168.html
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-7168
CWEs
CWE-294
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.