CVE-2026-7168 is an information-disclosure vulnerability in libcurl's reuse of proxy Digest-authentication state. After a transfer through one HTTP proxy using Digest authentication, reusing the same libcurl handle for a transfer through a different proxy can cause libcurl to send the Proxy-Authorization header intended for the first proxy to the second proxy. The flaw exposes proxy authentication material across proxy trust boundaries.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
27 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability referenced by the AlmaLinux local-security-check plugin; no technical vulnerability details are provided.
Unknown; the content provides only a reference link and no vulnerability details.
A vulnerability in curl/libcurl addressed by the Huawei EulerOS SA-2026-3408 security advisory; no technical flaw type is provided.
A specific vulnerability addressed by the EulerOS SA-2026-3495 curl/libcurl security update; no technical flaw details are provided.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.