Loading vulnerability…
curl/libcurl can leak credentials when configured to use a .netrc file for authentication and to follow HTTP redirects. Under certain circumstances, the password used for the original host can be sent to the redirect target host. According to the provided content, this occurs when the .netrc file contains an entry matching the redirect target hostname, but that entry omits the password field or omits both login and password. The issue is described as an exposure of sensitive information affecting curl-related integrations and downstream products that embed vulnerable curl/libcurl versions.
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.
.netrc-based credential use with automatic HTTP redirect following unless running a fixed version. As an operational mitigation, avoid incomplete .netrc entries for redirect target hosts, especially entries that omit the password or both login and password. Where possible, disable redirect following or avoid sending credentials via .netrc in affected workflows until patched.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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.