CVE-2026-8925
SASL double-free
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 8.16.1, 8.20.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: yes
- Technical impact: total
Summary
The curl logic that works with SASL authentication could end up cleaning up the GSASL context twice without clearing the pointer in between, making it `free()` the same pointer twice.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- curl curl
From 8.15.0 · fixed in 8.16.1; From 8.17.0 · fixed in 8.20.1
- curl curl
Version range not reported
- curl curl
8.20.0, 8.19.0, 8.18.0, 8.17.0, 8.16.0, 8.15.0