CVE-2025-10966: missing SFTP host verification with wolfSSH
Noroxi assessment
Priority: Monitor (action score 17/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.42% (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, b011e3fcfb06d6c0278595ee2ee297036fbe9793; azl3 cmake 3.30.3-11 on Azure Linux 3.0 3.30.3-12; azl3 cmake 3.30.3-12 on Azure Linux 3.0 3.30.3-12.
Low priority for now. Upgrade to curl curl 8.14.2, 8.16.1, b011e3fcfb06d6c0278595ee2ee297036fbe9793; azl3 cmake 3.30.3-11 on Azure Linux 3.0 3.30.3-12; azl3 cmake 3.30.3-12 on Azure Linux 3.0 3.30.3-12 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
curl's code for managing SSH connections when SFTP was done using the wolfSSH powered backend was flawed and missed host verification mechanisms. This prevents curl from detecting MITM attackers and more.
- Published
- Nov 7, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.4% · 37th percentile
- CWE
- CWE-322
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- 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.
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.
| Vendor | Product | CPE |
|---|---|---|
| haxx | curl | cpe:2.3:a:haxx:curl |
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.16.0, 8.15.0, 8.14.1, 8.14.0, 8.13.0, 8.12.1, 8.12.0, 8.11.1, 8.11.0, 8.10.1, 8.10.0, 8.9.1 … (+25)affected
- 7.69.0 and later · before 8.14.2affected · semver
- 8.15.0 and later · before 8.16.1affected · semver
- 6773c7ca65cf2183295e56603f9b86a5ce816a06 and later · before b011e3fcfb06d6c0278595ee2ee297036fbe9793affected · git
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- haxx curl7.69.0 and later · before 8.17.0
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 7.69.0 · before 8.17.0-r0 | 8.17.0-r0 |
| Debian:12 | curl | from 0 | — |
| Debian:14 | curl | before 8.17.0~rc2-1 | 8.17.0~rc2-1 |
| openSUSE:Tumbleweed | curl | before 8.17.0-1.1 | 8.17.0-1.1 |
| Red Hat:hummingbird:1 | curl | before 0:8.19.0-3.hum1 | 0:8.19.0-3.hum1 |
| Red Hat:hummingbird:1 | libcurl | before 0:8.19.0-3.hum1 | 0:8.19.0-3.hum1 |
| Red Hat:hummingbird:1 | libcurl-devel | before 0:8.19.0-3.hum1 | 0:8.19.0-3.hum1 |
| Red Hat:hummingbird:1 | libcurl-minimal | before 0:8.19.0-3.hum1 | 0:8.19.0-3.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…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-leak45Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-10148Sep 12, 2025 · predictable WebSocket mask21Monitor
- ← EarlierCVE-2025-9086Sep 12, 2025 · Out of bounds read for cookie path30Monitor
- Later →CVE-2025-13034Jan 8, 2026 · No QUIC certificate pinning with GnuTLS23Monitor
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 | b011e3fcfb06d6c0278595ee2ee297036fbe9793 | Vendor (CNA) |
| azl3 cmake 3.30.3-11 on Azure Linux 3.0 | 3.30.3-12 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 cmake 3.30.3-12 on Azure Linux 3.0 | 3.30.3-12 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 cmake 3.21.4-21 on CBL Mariner 2.0 | 3.21.4-22 · CBL-Mariner Releases | Microsoft (MSRC) |
| alpine:curl | 8.17.0-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:curl | 8.17.0~rc2-1 · Debian:14 | Package registry (OSV) |
| opensuse:curl | 8.17.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:curl | 0:8.19.0-3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl | 0:8.19.0-3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-devel | 0:8.19.0-3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-minimal | 0:8.19.0-3.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.
Credits
All researchersFinders, 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
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
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
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-322 · Key Exchange without Entity AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.