The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the pointer in betwee
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Jul 3, 2026
- Updated
- Sep 15, 2026
- EPSS
- 1.1% · 64th percentile
- CWE
- CWE-415
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| 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.15.0 and later · before 8.21.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.20.0, 8.19.0, 8.18.0, 8.17.0, 8.16.0, 8.15.0affected
- 8.15.0 and later · before 8.16.1affected · semver
- 8.17.0 and later · before 8.20.1affected · semver
- ab650379a8c25ca952f651476d25b4cdd77bb3fc and later · before 3da249e1f0716c06644ed3522a37a8bf81808012affected · 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.15.0 · before 8.22.0-r0 | 8.22.0-r0 |
| Alpine:v3.24 | curl | from 8.15.0 · before 8.21.0-r0 | 8.21.0-r0 |
| Debian:14 | curl | before 8.21.0~rc2-1 | 8.21.0~rc2-1 |
| openSUSE:Tumbleweed | curl | before 8.21.0-1.1 | 8.21.0-1.1 |
| Red Hat:hummingbird:1 | cargo | before 0:1.96.1-1.hum1 | 0:1.96.1-1.hum1 |
| Red Hat:hummingbird:1 | curl | before 0:8.21.0-0.1.hum1 | 0:8.21.0-0.1.hum1 |
| Red Hat:hummingbird:1 | rust | before 0:1.96.1-1.hum1 | 0:1.96.1-1.hum1 |
| Red Hat:hummingbird:1 | rust-debugger-common | before 0:1.96.1-1.hum1 | 0:1.96.1-1.hum1 |
Same product
haxx: all recordsOther 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 t50Plan
- 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-leak45Plan
- CVE-2019-5482Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.44Plan
- CVE-2017-8817The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and app42Plan
- CVE-2017-8816The NTLM authentication feature in curl and libcurl before 7.57.0 on 32-bit platforms allows attackers to cause a denial of service (integer42Plan
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 | 3da249e1f0716c06644ed3522a37a8bf81808012 | Vendor (CNA) |
| curl curl | 8.16.1 | Vendor (CNA) |
| curl curl | 8.20.1 | Vendor (CNA) |
| alpine:curl | 8.22.0-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:curl | 8.21.0~rc2-1 · Debian:14 | Package registry (OSV) |
| opensuse:curl | 8.21.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:cargo | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:curl | 0:8.21.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:rust | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:rust-debugger-common | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | 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.
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 researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Viktor Szakatsremediation developer
- Joshua Rogers (Aisle Research)finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-415 · Double FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.