incomplete mTLS config matching in conn reuse
Noroxi assessment
Priority: Monitor (action score 30/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.39% (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 7541ae569d82fb308a5e2d94916027da4fa3ba3e, 8.14.2, 8.16.1; azl3 curl 8.11.1-9 on Azure Linux 3.0 8.11.1-10.
Low priority for now. Upgrade to curl curl 7541ae569d82fb308a5e2d94916027da4fa3ba3e, 8.14.2, 8.16.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
libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them match too easily. In particular options related to the private key.
- Published
- Jul 3, 2026
- Updated
- Sep 15, 2026
- EPSS
- 0.4% · 32th percentile
- CWE
- CWE-305
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- 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
- Proof of concept exists, no weaponized module
- 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.7 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.7.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
- a1d6ad26100bc493c7b04f1301b1634b7f5aa8b4 and later · before 7541ae569d82fb308a5e2d94916027da4fa3ba3eaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | curl | before 8.12.1-4.el10_2.6 | 8.12.1-4.el10_2.6 |
| AlmaLinux:10 | libcurl | before 8.12.1-4.el10_2.6 | 8.12.1-4.el10_2.6 |
| AlmaLinux:10 | libcurl-devel | before 8.12.1-4.el10_2.6 | 8.12.1-4.el10_2.6 |
| AlmaLinux:10 | libcurl-minimal | before 8.12.1-4.el10_2.6 | 8.12.1-4.el10_2.6 |
| Alpine:v3.23 | curl | from 7.7 · before 8.22.0-r0 | 8.22.0-r0 |
| Alpine:v3.24 | curl | from 7.7 · before 8.21.0-r0 | 8.21.0-r0 |
| Debian:12 | curl | all versions | — |
| 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: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 |
| Red Hat:enterprise_linux:10.2 | curl | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
| Red Hat:enterprise_linux:10.2 | curl-debuginfo | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
| Red Hat:enterprise_linux:10.2 | curl-debugsource | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
| Red Hat:enterprise_linux:10.2 | libcurl | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
| Red Hat:enterprise_linux:10.2 | libcurl-debuginfo | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
| Red Hat:enterprise_linux:10.2 | libcurl-devel | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
| Red Hat:enterprise_linux:10.2 | libcurl-minimal | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
+25
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 | 7541ae569d82fb308a5e2d94916027da4fa3ba3e | Vendor (CNA) |
| curl curl | 8.14.2 | Vendor (CNA) |
| curl curl | 8.16.1 | Vendor (CNA) |
| curl curl | 8.20.1 | Vendor (CNA) |
| azl3 curl 8.11.1-9 on Azure Linux 3.0 | 8.11.1-10 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:curl | 8.12.1-4.el10_2.6 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:libcurl | 8.12.1-4.el10_2.6 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:libcurl-devel | 8.12.1-4.el10_2.6 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:libcurl-minimal | 8.12.1-4.el10_2.6 · AlmaLinux:10 | Package registry (OSV) |
| 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: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:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:curl-debugsource | 0:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libcurl | 0:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | 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:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libcurl-devel | 0:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | 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.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | 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:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | 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) |
| red hat:rust-debugger-common | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:rust-doc | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:rust-gdb | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
+2
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2026-06-26 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-21 |
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.
- First PoC-7 d
- Published
- TodayOct 15, 2026+105 d
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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-554551 days apartwrong reuse of HTTP Negotiate connection26Monitor
- CVE-2026-1965114 days apartbad reuse of HTTP Negotiate connection26Monitor
- CVE-2026-3784114 days apartwrong proxy connection reuse with credentials26Monitor
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
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-305 · Authentication Bypass by Primary WeaknessCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.