Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Unrated

curl SASL double-free

IdentifiersCVE-2026-8925CWE-415

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.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful triggering causes memory corruption conditions consistent with a double-free, which can lead to process crashes and potentially limited exploitation scenarios. The project assessed attacker control over the second free as difficult, but noted that server behavior can influence the sequence and timing sufficiently that malicious exploitation could not be ruled out. Practical impact is therefore primarily denial of service, with some risk of memory-corruption-based exploitation depending on allocator behavior and runtime conditions.

Mitigation

If you can’t patch tonight, do this now.

As a workaround, avoid using SASL-dependent protocols and flows affected by this bug, specifically IMAP, POP3, and SMTP, on builds linked with libgsasl. Reducing or disabling exposure to those protocol paths limits reachability until patched binaries can be deployed.

Remediation

Patch, then assume compromise.

Upgrade to curl 8.21.0 or later, which contains the fix for CVE-2026-8925. If immediate upgrade is not possible, apply the upstream patch locally. The provided content states the issue was fixed by commit 3da249e1f0716c06644ed3522.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.