What happened
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.
Affected versions
curl: 8.15.0 through before 8.16.1 (semver); 8.17.0 through before 8.20.1 (semver); ab650379a8c25ca952f651476d25b4cdd77bb3fc through before 3da249e1f0716c06644ed3522a37a8bf81808012 (git); 8.20.0; 8.19.0; 8.18.0; 8.17.0; 8.16.0; 8.15.0 Fixed: See vendor advisory.
Why it matters
Review the vendor advisory and exposure of the affected product to determine operational impact.
Detection & mitigation
- Apply vendor-provided updates or mitigations.
- Review affected product exposure and access logs.
Public PoC references
RepositoryAuthorFirst seenReference
hackerone.comNVD reference2026-07-03VerifiedSource timeline
CVE record published by NVDView source ↗
Record history
Record created from the first normalized source observation.
Metadata and source references refreshed.