curl SASL double-free
CVE-2026-8925 is a medium-severity double-free vulnerability in curl/libcurl's SASL authentication handling when curl is built with libgsasl. In SASL-enabled protocol flows, curl's logic can clean up the GSASL context twice without clearing the pointer between cleanup operations, resulting in free() being called twice on the same pointer. The issue affects SASL-capable protocols including IMAP, POP3, and SMTP, and is reachable via both the curl command-line tool and libcurl integrations. According to the provided content, the flaw was introduced by commit ab650379a8c25ca952f6 and affects curl versions 8.15.0 through 8.20.0 inclusive.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A double-free vulnerability in curl's SASL authentication handling where the same GSASL context could be freed twice in SASL-enabled protocol flows.
A double-free vulnerability in curl/libcurl SASL authentication flows involving the GSASL context, potentially leading to memory corruption or crashes.
A curl/libcurl double-free vulnerability.
A medium-severity curl/libcurl vulnerability involving a double-free condition in SASL handling.
The version that knows your environment.
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.