CVE-2026-8925Published Jul 3, 2026 · Jul 3Updated Oct 28
SASL double-free
curl
Critical9.8Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
curl
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
8.17.08.16.08.15.0| No fix yet |
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.
From the CVE record · curl
Curl's SASL authentication logic can clean up a GSASL context twice without clearing its pointer, causing a double-free. The input does not specify how an attacker could trigger this or whether network access, authentication, or user interaction is required.
Engineers running curl should check their installations; affected versions are not specified.