CVE-2026-107929: local interface connection reuse mixup
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.66% (FIRST EPSS); higher than 52.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: azl3 curl 8.11.1-12 on Azure Linux 3.0 Release Notes; azl3 rust 1.75.0-31 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to azl3 curl 8.11.1-12 on Azure Linux 3.0 Release Notes; azl3 rust 1.75.0-31 on Azure Linux 3.0 Release Notes 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 `CURLOPT_INTERFACE` (or the command line tool's `--interface` option) is set with one of the documented prefixes (`if!`, `host!`, `ifhost!`), that binding is not part of the connection reuse key, so a later transfer asking for a different source can silently reuse an existing connection and go out from the earlier transfer's source address
- Published
- Oct 20, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- CWE-488
Report tools
Action score
32
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
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.
Is your version affected? Check itNoroxi 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.
—
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.22.0 and later · up to and including 8.22.0affected · semver
- 8.21.0 and later · up to and including 8.21.0affected · semver
- 8.20.0 and later · up to and including 8.20.0affected · semver
- 8.19.0 and later · up to and including 8.19.0affected · semver
- 8.18.0 and later · up to and including 8.18.0affected · semver
- 8.17.0 and later · up to and including 8.17.0affected · semver
- 8.16.0 and later · up to and including 8.16.0affected · semver
- 8.15.0 and later · up to and including 8.15.0affected · semver
- 8.14.1 and later · up to and including 8.14.1affected · semver
- 8.14.0 and later · up to and including 8.14.0affected · semver
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 | before 8.23.0-r0 | 8.23.0-r0 |
| Debian:13 | curl | from 0 | — |
| openSUSE:Tumbleweed | curl | before 8.23.0-1.1 | 8.23.0-1.1 |
| Red Hat:hummingbird:1 | curl | before 0:8.23.0-0.1.hum1 | 0:8.23.0-0.1.hum1 |
| Red Hat:hummingbird:1 | libcurl | before 0:8.23.0-0.1.hum1 | 0:8.23.0-0.1.hum1 |
| Red Hat:hummingbird:1 | libcurl-devel | before 0:8.23.0-0.1.hum1 | 0:8.23.0-0.1.hum1 |
| Red Hat:hummingbird:1 | libcurl-minimal | before 0:8.23.0-0.1.hum1 | 0:8.23.0-0.1.hum1 |
| SUSE:Linux Enterprise Installer Updates 15 SP4 | curl | before 8.14.1-150400.5.98.1 | 8.14.1-150400.5.98.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | curl | before 8.22.0-150700.7.33.1 | 8.22.0-150700.7.33.1 |
| SUSE:Linux Enterprise Server 15 SP6-LTSS | curl | before 8.22.0-150600.4.58.1 | 8.22.0-150600.4.58.1 |
Same product
curl: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-94265Authorization: Negotiate sent to foreign origin36Monitor
- CVE-2026-92388FTP wildcard write callback mixup36Monitor
- CVE-2026-87866wolfSSL public-key pinning bypass36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-86413Oct 20, 2026 · Negotiate credentials sent to redirected origin36Monitor
- ← EarlierCVE-2026-107928Oct 20, 2026 · info leak uploading over WebSockets with GnuTLS32Monitor
- Later →CVE-2026-86414Oct 20, 2026 · leaking host credentials to HTTP proxy36Monitor
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 |
|---|---|---|
| azl3 curl 8.11.1-12 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 rust 1.75.0-31 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| alpine:curl | 8.23.0-r0 · Alpine:v3.23 | Package registry (OSV) |
| opensuse:curl | 8.23.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:curl | 0:8.23.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl | 0:8.23.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-devel | 0:8.23.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-minimal | 0:8.23.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:curl | 8.14.1-150400.5.98.1 · SUSE:Linux Enterprise Installer Updates 15 SP4 | 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.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+23 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Maksim Hayderfinder
- Stefan Eissingremediation 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-864110 days apartFTP connection reuse inherits client-certificate36Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: patch commit or PR link.
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.
- Special conditions such as timing or configuration are required.
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
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-488 · Exposure of Data Element to Wrong SessionCVSS vector
CVSS:3.1/AV:N/AC:H/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.
Attack patterns (CAPEC)
Change log
- CVSS— → 8.1
- Severity— → high
- SSVC exploitation— → poc
- Fix✗ → ✓
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.