CVE-2026-8925: SASL double-free
Published Jul 3, 2026
·Updated
Last updated 2 July 2026
Other sources
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.
— NVD
Affected Software
3 affected componentsFixes available
haxx curl>=8.15.0<8.21.0
debian/curl
7.88.1-10+deb12u157.88.1-10+deb12u58.14.1-2+deb13u58.14.1-2+deb13u78.23.0-28.24.0~rc1-1
IBM API Connect<=V10.0.8.0 - V10.0.8.13
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/curlto a version that resolves this vulnerability.Fixed in 7.88.1-10+deb12u15Fixed in 7.88.1-10+deb12u5Fixed in 8.14.1-2+deb13u5Fixed in 8.14.1-2+deb13u7Fixed in 8.23.0-2Fixed in 8.24.0~rc1-1
Event History
Jul 3, 2026
CVE Published
via MITRE·06:15 AM
Data Sourced
via MITRE·06:15 AM
DescriptionWeakness
Data Sourced
via Red Hat·07:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·07:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Nov 18, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-8925?
CVE-2026-8925 has a risk level of 21.
2
What causes CVE-2026-8925?
CVE-2026-8925 is caused by the curl logic that incorrectly cleans up the GSASL context twice.
3
How do I fix CVE-2026-8925?
To fix CVE-2026-8925, you should upgrade to the latest version of curl that contains the patch for this vulnerability.
4
Which software is affected by CVE-2026-8925?
CVE-2026-8925 affects the Debian version of curl.
5
What type of vulnerability is CVE-2026-8925?
CVE-2026-8925 is classified as a double free vulnerability.