curl: Use After Free
CVE-2026-9080 is a high-severity use after free vulnerability in curl, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 8.14.2, 8.16.1, 8.20.1 as the first without the flaw, so updating curl to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.49% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update curl to 8.14.2 or 8.16.1 or 8.20.1 or 5ab34cba42e4ee4282fe8bab43f311d51b9bf9bd, whichever matches your release line, or a later version.
- Read the advisory on curl.se for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Curl | curl | 8.13.0 up to, but not including, 8.14.2; 8.15.0 up to, but not including, 8.16.1; 8.17.0 up to, but not including, 8.20.1; cfc657a48dbafb4194676d4c9d841388b3a22210 up to, but not including, 5ab34cba42e4ee4282fe8bab43f311d51b9bf9bd; 8.20.0; 8.19.0; 8.18.0; 8.17.0; and 5 more ranges | 8.14.2, 8.16.1, 8.20.1, 5ab34cba42e4ee4282fe8bab43f311d51b9bf9bd |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. Scored by CISA (ADP).
Official description
Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION` callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer's memory has been freed.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- hackerone.com/reports/3749204Exploit, Issue Tracking, Third Party Advisory
Other vulnerabilities in curl
- 7.5 High severity
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 9.1 Critical severity
Recent Use After Free vulnerabilities
- 9.8 Critical severity
- 8.1 High severity
- 8.0 High severity
- 8.8 High severity
- 7.5 High severity
- 9.6 Critical severity
Spotted an error? Tell us.