Skip to main content

curl CVE-2026-12064

| EUVDEUVD-2026-41502 HIGH
Improper Certificate Validation (CWE-295)
7.5
CVSS 3.1 · Vendor
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Position as MITM on SSH path
  2. Delivery
    Wait for curl schemeless '--proto-default sftp/scp' call
  3. Exploit
    Host-key verification silently skipped
  4. Execution
    Present spoofed SFTP/SCP server
  5. Impact
    Intercept credentials and tamper with transferred data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Certificate validation
Exploitation Conditions

Exploitation requires all of: (1) the victim invoking curl with a schemeless URL combined with '--proto-default sftp' or '--proto-default scp' (equivalently CURLOPT_DEFAULT_PROTOCOL set to sftp/scp) - this exact non-default invocation is the trigger; (2) an active man-in-the-middle position on the SSH connection path to impersonate the SFTP/SCP server; and (3) the victim using SFTP/SCP transfers at all. Limiting factors that reduce real-world risk: it does NOT trigger when an explicit scheme is present in the URL, it requires network interception rather than mere reachability, and it depends on a specific command-line usage pattern that is not curl's default behavior. The CVSS vector is PR:N (no attacker authentication), but the practical barrier is the MITM position plus the specific victim configuration.

Impact

Signals are mixed and point to a real-but-conditional integrity risk rather than a mass-exploitation emergency. The NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:N/I:H/A:N, score 7.5) treats it as network, low-complexity, unauthenticated with high integrity impact, but this understates two limiting factors: a successful attack requires an active man-in-the-middle position on the SSH path AND a victim running a non-default invocation (schemeless URL with --proto-default sftp/scp), which in practice argues for higher attack complexity than AC:L. EPSS is low (0.21%, 11th percentile), consistent with the narrow preconditions, and there is no KEV listing and no public exploit identified, so there is no evidence of active or widespread exploitation. NVD scores no confidentiality/availability impact, though a MITM who defeats host verification can typically read transferred data too, so C:N is arguably conservative. Net: prioritize for environments that script curl SFTP/SCP transfers with default-protocol flags, but this is not a drop-everything issue for the general population.

Exploit ScenarioDerived

An attacker positioned on the network path (e.g. rogue Wi-Fi, ARP/DNS spoofing, or a compromised upstream hop) waits for a script or user that runs 'curl --proto-default sftp user@host/path' with a schemeless target. Because curl skips host-key verification for this invocation, the attacker's spoofed SSH server is accepted without a mismatch error, letting them intercept credentials/data or serve tampered files. No public exploit is identified at time of analysis, and the attack requires the MITM position plus the specific default-protocol invocation.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv5 – Jul 06, 2026

SSH host-key verification bypass in curl/libcurl (versions through 8.20.0) lets a network man-in-the-middle silently impersonate an SFTP/SCP server when a user invokes curl with a schemeless URL plus '--proto-default sftp' (or scp). In this specific invocation the command-line tool layer misidentifies the scheme and skips setting CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS, while libcurl still honors CURLOPT_DEFAULT_PROTOCOL and completes the connection, so curl connects to an unverified host without any error. Tagged an Authentication Bypass; EPSS is low (0.21%, 11th percentile) and no public exploit was identified at time of analysis.

Earlier versions of this analysis (4)
v4 Jul 06, 2026 - 21:49 cvss changed CVSS 7.5

SSH host-key verification bypass in curl's command-line tool layer affects releases from 7.81.0 through 8.20.0 when a schemeless URL is combined with --proto-default sftp (or scp). The tool mis-infers the scheme and skips initialization of CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS, so libcurl still establishes the SFTP/SCP connection but without host verification and without raising an error, enabling silent man-in-the-middle interception. EPSS is low (0.21%, 11th percentile), no public exploit is identified at time of analysis, and it is not on CISA KEV.

v3 Jul 06, 2026 - 21:47 cvss changed CVSS 7.5

SSH host verification bypass in the curl command-line tool (versions through 8.20.0) lets a schemeless URL combined with --proto-default sftp (or scp) silently connect to an unverified SSH remote host. The curl tool layer misinfers the scheme and skips initialization of CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS, while libcurl still honors CURLOPT_DEFAULT_PROTOCOL and completes the SFTP/SCP connection - so host key checking is omitted with no error raised. Tagged as an Authentication Bypass; no public exploit identified at time of analysis, and EPSS is low (0.21%, 11th percentile).

v2 Jul 06, 2026 - 21:47 cvss changed CVSS 7.5

Silent SSH host verification bypass in curl/libcurl allows an attacker positioned to intercept traffic to impersonate an SFTP/SCP server when a victim invokes curl with a schemeless URL and --proto-default sftp (or scp). A desync between the curl tool layer and libcurl causes the tool to misinfer the scheme and skip initializing CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS, while libcurl still honors CURLOPT_DEFAULT_PROTOCOL and completes the connection - so curl connects to an unverified SSH host with no error. Tagged an authentication bypass; no public exploit identified at time of analysis, and EPSS risk is low at 0.21% (11th percentile).

v1 Jun 24, 2026 - 18:31

SSH host verification is silently bypassed in the curl command line tool (versions 7.81.0-8.20.0) when a schemeless URL is combined with the --proto-default sftp or --proto-default scp flag. A disconnect between the tool layer and libcurl causes the tool to misinfer the URL scheme and skip initialization of CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS, leaving the SSH connection unverified without any error. This enables a network-positioned attacker to perform a man-in-the-middle attack against SFTP or SCP sessions initiated under these specific conditions. No public exploit is identified at time of analysis, and no KEV listing exists; the curl project rates this LOW severity and the flaw is limited exclusively to the curl CLI, not the libcurl library.

RemediationAI

Upgrade to a fixed curl/libcurl release as published in the vendor advisory at https://curl.se/docs/CVE-2026-12064.html and the oss-security announcement at https://seclists.org/oss-sec/2026/q2/1012 - no vendor-released patch version is stated in the provided data, so confirm the exact fixed version directly from the curl.se advisory before deploying. Until patched, avoid the vulnerable pattern: do not rely on '--proto-default sftp/scp' with schemeless URLs; instead always supply an explicit scheme in the URL (e.g. sftp://host/path), which routes through the tool code path that installs the host-key options. As a stronger compensating control, pass an explicit host-key fingerprint on every SSH transfer (curl --hostpubsha256 <hash>) or force a known_hosts file (--knownhosts / config), so a missing verification option causes a failure instead of a silent unverified connection; the trade-off is that these must be maintained per host and will break automation if fingerprints rotate. Where feasible, run curl SFTP/SCP transfers only over trusted network paths to reduce MITM exposure.

Affected VersionsENISA

curl 8.14.0 ≤8.14.0
curl 8.8.0 ≤8.8.0
curl 7.81.0 ≤7.81.0
curl 8.9.0 ≤8.9.0
curl 7.87.0 ≤7.87.0
curl 8.3.0 ≤8.3.0
curl 8.1.1 ≤8.1.1
curl 8.2.1 ≤8.2.1
curl 8.5.0 ≤8.5.0
curl 8.4.0 ≤8.4.0
curl 7.83.0 ≤7.83.0
curl 8.12.1 ≤8.12.1
curl 8.18.0 ≤8.18.0
curl 7.88.0 ≤7.88.0
curl 8.0.0 ≤8.0.0
curl 7.82.0 ≤7.82.0
curl 8.7.1 ≤8.7.1
curl 8.11.0 ≤8.11.0
curl 7.84.0 ≤7.84.0
curl 8.1.0 ≤8.1.0
curl 8.0.1 ≤8.0.1
curl 8.1.2 ≤8.1.2
curl 8.17.0 ≤8.17.0
curl 8.10.0 ≤8.10.0
curl 8.15.0 ≤8.15.0
curl 7.88.1 ≤7.88.1
curl 8.10.1 ≤8.10.1
curl 8.16.0 ≤8.16.0
curl 8.7.0 ≤8.7.0
curl 7.83.1 ≤7.83.1
curl 8.9.1 ≤8.9.1
curl 8.2.0 ≤8.2.0
curl 7.85.0 ≤7.85.0
curl 8.14.1 ≤8.14.1
curl 8.11.1 ≤8.11.1
curl 8.19.0 ≤8.19.0
curl 8.6.0 ≤8.6.0
curl 8.12.0 ≤8.12.0
curl 8.20.0 ≤8.20.0
curl 7.86.0 ≤7.86.0
curl 8.13.0 ≤8.13.0

Affected Packages

euvd curl no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected technology is curl's SSH-based file transfer support (SFTP/SCP), which relies on an underlying SSH library (libssh2/libssh) beneath libcurl. Host authenticity is normally enforced either by known_hosts matching (CURLOPT_SSH_KNOWNHOSTS) or an explicit host public-key fingerprint (CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256). The root cause is a desynchronization between the curl command-line tool and libcurl over how the default protocol is resolved: the tool infers the scheme from the (absent) URL scheme rather than from --proto-default/CURLOPT_DEFAULT_PROTOCOL, so the tool code path that wires up the SSH verification options is never reached, whereas libcurl independently resolves the protocol to SFTP/SCP and proceeds to connect. Although NVD lists CWE as N/A, the behavior is a classic Improper Certificate/Host-Key Validation and Key Exchange Without Entity Authentication class (CWE-295 / CWE-322): the encrypted transport is established but the remote endpoint's identity is never verified.

Know when Curl gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (CNA) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 7.4 HIGH

Requires an active MITM position plus a specific non-default invocation (AC:H); no attacker auth (PR:N); defeated host verification exposes both intercepted data (C:H) and tampering (I:H), with no availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
SUSE 7.4 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Red Hat 7.5 HIGH

Primary rating from Vendor (CNA).

CVSS VectorVendor

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

5
Analysis Updated
Jul 06, 2026 - 21:49 vuln.today
v5 - CVSS changed
Analysis Updated
Jul 06, 2026 - 21:49 vuln.today
v4 - CVSS changed
Analysis Updated
Jul 06, 2026 - 21:47 vuln.today
v3 - CVSS changed
Analysis Updated
Jul 06, 2026 - 21:47 vuln.today
v2 - CVSS changed
CVSS changed
Jul 06, 2026 - 19:22 NVD
7.5 (HIGH)

Description PRE-NVD

Disclosed via oss-security. NVD scoring and full description are pending.

Executive ViewAI

Why It Matters

curl/libcurl versions through 8.20.0 contain an SSH host-key verification bypass that allows attackers positioned on the network to silently impersonate SFTP/SCP servers when curl is invoked with specific command-line parameters. This exposes organizations to credential theft and data interception during file transfers if deployments use vulnerable invocation patterns. Risk is elevated for infrastructure automation, CI/CD pipelines, and system administration scripts relying on curl.

Business Impact: High
Compensating Controls

Require all curl SFTP/SCP invocations to use fully-qualified URLs with explicit sftp:// or scp:// schemes; disable or restrict '--proto-default' flag usage through script review and configuration controls; implement network segmentation to limit SSH/SFTP traffic to authorized endpoints only; enable SSH connection logging and SFTP monitoring to detect unexpected host verification failures.

Threat Intelligence Overview

EPSS Score
0.2%
Top 89% exploitable
Prevalence
Ubiquitous
curl/libcurl ships in nearly all Linux, container, and enterprise environments
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in Curl

View all
CVE-2021-22901 HIGH POC
8.1 Jun 11

curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when

CVE-2013-0249 HIGH POC
7.5 Mar 08

Stack-based buffer overflow in the Curl_sasl_create_digest_md5_message function in lib/curl_sasl.c in curl and libcurl 7

CVE-2015-3145 HIGH
7.5 Apr 24

The sanitize_cookie_path function in cURL and libcurl 7.31.0 through 7.41.0 does not properly calculate an index, which

CVE-2022-32206 MEDIUM POC
6.5 Jul 07

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple t

CVE-2022-32207 CRITICAL POC
9.8 Jul 07

When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the

CVE-2022-43551 HIGH POC
7.5 Dec 23

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Rated high seve

CVE-2022-32221 CRITICAL POC
9.8 Dec 05

When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data t

CVE-2018-0500 CRITICAL POC
9.8 Jul 11

Curl_smtp_escape_eob in lib/smtp.c in curl 7.54.1 to and including curl 7.60.0 has a heap-based buffer overflow that mig

CVE-2022-32205 MEDIUM POC
4.3 Jul 07

A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 sto

CVE-2025-9086 HIGH POC
7.5 Sep 12

1. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack co

CVE-2023-23914 CRITICAL POC
9.1 Feb 23

A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functional

CVE-2023-27534 HIGH POC
8.8 Mar 30

A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly re

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SLES15-SP5-CHOST-BYOS-SAP-CCloud Affected
SLES15-SP6-CHOST-BYOS Affected
SLES15-SP6-CHOST-BYOS-Aliyun Affected
SLES15-SP6-CHOST-BYOS-Azure Affected
SLES15-SP6-CHOST-BYOS-EC2 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy