wrong STARTTLS connection reuse
Noroxi assessment
Priority: Monitor (action score 32/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.30% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: curl curl 8.14.2, 8.16.1, 8.20.1; azl3 curl 8.11.1-9 on Azure Linux 3.0 8.11.1-10.
Low priority for now. Upgrade to curl curl 8.14.2, 8.16.1, 8.20.1; azl3 curl 8.11.1-9 on Azure Linux 3.0 8.11.1-10 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
A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.
- EUVD-2026-41503
- ALSA-2026:55439
- ALSA-2026:57462
- openSUSE-SU-2026:11230-1
- openSUSE-SU-2026:21272-1
- RHSA-2026:29017
- RHSA-2026:34975
- RHSA-2026:55439
- RHSA-2026:55450
- RHSA-2026:57462
- RHSA-2026:72506
- RLSA-2026:55439
- RLSA-2026:57462
- SUSE-SU-2026:22553-1
- SUSE-SU-2026:22582-1
- SUSE-SU-2026:22709-1
- SUSE-SU-2026:22889-1
- SUSE-SU-2026:2925-1
- SUSE-SU-2026:2926-1
- SUSE-SU-2026:3043-1
- Published
- Jul 3, 2026
- Updated
- Sep 15, 2026
- EPSS
- 0.3% · 22th percentile
- CWE
- CWE-295
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
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
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 helpAffected 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 curl7.30.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.0, 8.14.1, 8.14.0, 8.13.0, 8.12.1, 8.12.0, 8.11.1 … (+24)affected
- 7.30.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
- a1701eea289fe7ea80651f801cf992838a491dde and later · before a86efdd7ca5433de9231e650f18247de8319ad16affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | curl | before 7.61.1-34.el8_10.13 | 7.61.1-34.el8_10.13 |
| AlmaLinux:8 | libcurl | before 7.61.1-34.el8_10.13 | 7.61.1-34.el8_10.13 |
| AlmaLinux:8 | libcurl-devel | before 7.61.1-34.el8_10.13 | 7.61.1-34.el8_10.13 |
| AlmaLinux:8 | libcurl-minimal | before 7.61.1-34.el8_10.13 | 7.61.1-34.el8_10.13 |
| AlmaLinux:9 | curl | before 7.76.1-40.el9_8.5 | 7.76.1-40.el9_8.5 |
| AlmaLinux:9 | curl-minimal | before 7.76.1-40.el9_8.5 | 7.76.1-40.el9_8.5 |
| AlmaLinux:9 | libcurl | before 7.76.1-40.el9_8.5 | 7.76.1-40.el9_8.5 |
| AlmaLinux:9 | libcurl-devel | before 7.76.1-40.el9_8.5 | 7.76.1-40.el9_8.5 |
| AlmaLinux:9 | libcurl-minimal | before 7.76.1-40.el9_8.5 | 7.76.1-40.el9_8.5 |
| Alpine:v3.23 | curl | from 7.30.0 · before 8.22.0-r0 | 8.22.0-r0 |
| Alpine:v3.24 | curl | from 7.30.0 · before 8.21.0-r0 | 8.21.0-r0 |
| Debian:12 | curl | all versions | — |
| Debian:13 | curl | before 8.14.1-2+deb13u7 | 8.14.1-2+deb13u7 |
| Debian:14 | curl | before 8.21.0~rc2-1 | 8.21.0~rc2-1 |
| openSUSE:Leap 16.0 | curl | before 8.14.1-160000.8.1 | 8.14.1-160000.8.1 |
| openSUSE:Tumbleweed | curl | before 8.21.0-1.1 | 8.21.0-1.1 |
| Red Hat:enterprise_linux_eus:10.0 | curl | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | curl-debuginfo | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | curl-debugsource | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | libcurl | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | libcurl-debuginfo | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | libcurl-devel | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | libcurl-minimal | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | libcurl-minimal-debuginfo | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
+60
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 t51Plan
- 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-2022-32207When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a ren43Plan
- 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
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 | 8.14.2 | Vendor (CNA) |
| curl curl | 8.16.1 | Vendor (CNA) |
| curl curl | 8.20.1 | Vendor (CNA) |
| curl curl | a86efdd7ca5433de9231e650f18247de8319ad16 | Vendor (CNA) |
| azl3 curl 8.11.1-9 on Azure Linux 3.0 | 8.11.1-10 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:curl | 7.76.1-40.el9_8.5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:curl-minimal | 7.76.1-40.el9_8.5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:libcurl | 7.76.1-40.el9_8.5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:libcurl-devel | 7.76.1-40.el9_8.5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:libcurl-minimal | 7.76.1-40.el9_8.5 · AlmaLinux:9 | Package registry (OSV) |
| alpine:curl | 8.22.0-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:curl | 8.14.1-2+deb13u7 · Debian:13 | 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:clippy | 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:curl-debuginfo | 0:7.76.1-40.el9_8.5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:curl-debugsource | 0:7.76.1-40.el9_8.5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:curl-minimal | 0:7.76.1-40.el9_8.5 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:curl-minimal-debuginfo | 0:7.76.1-40.el9_8.5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libcurl | 0:7.76.1-40.el9_8.5 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:libcurl | 0:8.21.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-debuginfo | 0:7.76.1-40.el9_8.5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libcurl-devel | 0:7.76.1-40.el9_8.5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libcurl-devel | 0:8.21.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-minimal | 0:8.21.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-minimal-debuginfo | 0:7.76.1-40.el9_8.5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:rust | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:rust-analyzer | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
+7
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.
- Stefan Eissingremediation developer
- Andrew Nesbitt (powered by Mythos)finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-115640 days apartNative CA trust persist36Monitor
- CVE-2026-8023065 days apartOpenSSL pinning bypass30Monitor
- CVE-2026-8220865 days apartwolfSSL CA-cache hit overrides callback30Monitor
- CVE-2025-4947401 days apartQUIC certificate check skip with wolfSSL26Monitor
- CVE-2025-13034176 days apartNo QUIC certificate pinning with GnuTLS23Monitor
- CVE-2026-700951 days apartOCSP stapling bypass with Apple SecTrust21Monitor
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.
- A low-privileged account is enough.
- 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
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
nvd-secondary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) { // Left empty for the test environment}Fixed
val client = OkHttpClient.Builder() .certificatePinner( CertificatePinner.Builder() .add("api.sirius.example", "sha256/…") .build() ).build()Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.