NVD / CVE Program· CNA curl

CVE-2026-80229: OpenSSL provider use-after-free

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.56% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: curl curl 7ea37abc6ac0120ba5f6d94be8d196f7cf1506bb, 8.14.2, 8.16.1.

Low priority for now. Upgrade to curl curl 7ea37abc6ac0120ba5f6d94be8d196f7cf1506bb, 8.14.2, 8.16.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Sep 6, 2026
Updated: Sep 15, 2026
EPSS: 0.5% · 46th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
haxx	curl	cpe:2.3:a:haxx:curl

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

haxx curl8.14.0 and later · before 8.22.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (curl). Independent of NVD's CPE analysis and usually ahead of it.

curl curl
- 8.21.0, 8.20.0, 8.19.0, 8.18.0, 8.17.0, 8.16.0, 8.15.0, 8.14.1, 8.14.0affected
- 8.14.0 and later · before 8.14.2affected · semver
- 8.15.0 and later · before 8.16.1affected · semver
- 8.17.0 and later · before 8.20.1affected · semver
- 8.21.0 and later · before 8.22.0affected · semver
- f2ce6c46b9dcc46ced0ce43fa95176ea7599a854 and later · before 7ea37abc6ac0120ba5f6d94be8d196f7cf1506bbaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.23	curl	from 8.14.0 · before 8.22.0-r0	8.22.0-r0
Debian:13	curl	from 0	—
Debian:14	curl	before 8.22.0~rc3-1	8.22.0~rc3-1
openSUSE:Leap 16.0	curl	before 8.14.1-160000.9.1	8.14.1-160000.9.1
openSUSE:Tumbleweed	curl	before 8.22.0-1.1	8.22.0-1.1
Red Hat:hummingbird:1	curl	before 0:8.22.0-0.1.hum1	0:8.22.0-0.1.hum1
Red Hat:hummingbird:1	libcurl	before 0:8.22.0-0.1.hum1	0:8.22.0-0.1.hum1
Red Hat:hummingbird:1	libcurl-devel	before 0:8.22.0-0.1.hum1	0:8.22.0-0.1.hum1
Red Hat:hummingbird:1	libcurl-minimal	before 0:8.22.0-0.1.hum1	0:8.22.0-0.1.hum1
SUSE:Linux Enterprise Micro 5.3	curl	before 8.14.1-150400.5.91.1	8.14.1-150400.5.91.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7	curl	before 8.14.1-150700.7.26.1	8.14.1-150700.7.26.1
SUSE:Linux Enterprise Server 15 SP6-LTSS	curl	before 8.14.1-150600.4.51.1	8.14.1-150600.4.51.1
SUSE:Linux Enterprise Server 16.0	curl-mini	before 8.14.1-160000.9.1	8.14.1-160000.9.1
SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5	curl	before 8.0.1-11.129.1	8.0.1-11.129.1
SUSE:Linux Micro 6.1	curl	before 8.14.1-slfo.1.1_10.1	8.14.1-slfo.1.1_10.1
SUSE:Linux Micro 6.2	curl	before 8.14.1-160000.9.1	8.14.1-160000.9.1

Same product

haxx: all records

Other highest-scoring records for the same primary product.

CVE-2021-22901curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session t
51Plan
CVE-2023-38039When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.
47Plan
CVE-2024-2398HTTP/2 push headers memory-leak
45Plan

Published before and after this one in the same product

← EarlierCVE-2026-18924Sep 6, 2026 · HTTP/2 server push UAF
36Monitor
← EarlierCVE-2026-19931Sep 6, 2026 · Negotiate ambient user conn reuse
39Monitor
Later →CVE-2026-80230Sep 6, 2026 · OpenSSL pinning bypass
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
curl curl	7ea37abc6ac0120ba5f6d94be8d196f7cf1506bb	Vendor (CNA)
curl curl	8.14.2	Vendor (CNA)
curl curl	8.16.1	Vendor (CNA)
curl curl	8.20.1	Vendor (CNA)
curl curl	8.22.0	Vendor (CNA)
azl3 rust 1.75.0-30 on Azure Linux 3.0	—	Microsoft (MSRC)
alpine:curl	8.22.0-r0 · Alpine:v3.23	Package registry (OSV)
debian:curl	8.22.0~rc3-1 · Debian:14	Package registry (OSV)
opensuse:curl	8.22.0-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:curl	0:8.22.0-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:libcurl	0:8.22.0-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:libcurl-devel	0:8.22.0-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:libcurl-minimal	0:8.22.0-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
suse:curl	8.14.1-160000.9.1 · SUSE:Linux Micro 6.2	Package registry (OSV)
suse:curl-mini	8.14.1-160000.9.1 · SUSE:Linux Enterprise Server 16.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Stanislav Fort (Aisle Research)finder
Daniel Stenbergremediation developer

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-1053665 days apartHTTP/2 stream-dependency tree UAF
39Monitor
CVE-2026-189240 days apartHTTP/2 server push UAF
36Monitor
CVE-2026-3805179 days apartuse after free in SMB connection reuse
30Monitor
CVE-2026-908065 days apartUAF after pause in socket callback
29Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

curl.se/docs/CVE-2026-80229.html

Show all references (1 more)

curl.se/docs/CVE-2026-80229.json

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records