AIKIDO-2026-185362
libcurl is vulnerable to Use After Free
37
Low Risk
This Affects:
libcurlTL;DR
On the multi interface, a pooled TLS connection can outlive the easy handle that created it. With an OpenSSL 3 provider, libcurl attaches a library context to that handle and does not take an ownership reference, so destroying the handle frees the context while the live connection still points at it. Later I/O then uses the freed context. The fix keeps the provider context alive for the connection, and avoids reuse when a provider is in use.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you use the multi interface with an OpenSSL 3 provider.
Background info
libcurl is vulnerable to Use After Free in versions 8.14.0 - 8.21.0.
How to fix this
Upgrade the libcurl and/or the curl.curl library to the patch version.
Links
GitHub Release
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.