CVE-2026-9547

SSH improper host validation

Published Jul 3, 2026 CVSS 3.1 · 7.4 High EPSS < 1% KEV · Not listed
Description
When a libcurl-based application performs transfers via `SCP://` or `SFTP://`
and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an
untrusted server. This vulnerability occurs when a server presents a host key
type that does not match the specific key type already recorded for that host
in the `known_hosts` file. Instead of rejecting the mismatch, the callback
mechanism fails to properly enforce the restriction, allowing the connection
to succeed without warning and risking a potential man-in-the-middle attack.

Analysis

AI-generated

Technical impact

The CVE involves the libcurl library mis‑enforcing SSH host key validation when using the CURLOPT_SSH_KEYFUNCTION callback for SCP or SFTP transfers. When a server presents a host key type that does not match the type already recorded for that host in the known_hosts file, the callback silently allows the connection. This weakness, classified as CWE‑347, permits an attacker who controls an impersonating SSH server to conduct a man‑in‑the‑middle attack without the client being alerted.

Affected Systems

Any application that bundles the SFTP transfers with the CURLOPT_SSH_KEYFUNCTION callback is potentially vulnerable. The product is the c is provided, so administrators must verify whether their installed libcurl contains the flaw.

Risk and Exploitability

The CVSS score of 7.4 indicates high severity, while an EPSS score below 1 % The vulnerability is not listed in CISA KEV. Exploitation requires an attacker to impersonate an SSH server presenting a mismatched host key type; the client will accept the connection silently.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a libcurl release that correctly enforces host key validation.
  • If an upgrade is not immediately possible, callback with custom logic that verifies the key type against the known_hosts entry before initiating the transfer.
  • Disable SCP or SFTP transfers to untrusted hosts until the vulnerability is patched, or enforce manual confirmation of host keys prior to connection establishment.

Generated by OpenCVE AI on September 21, 2026 at 07:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8487-1 curl vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-297
Type Values Removed Values Added
Weaknesses CWE-295
CWE-307
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-295
CWE-307
Type Values Removed Values Added
Weaknesses CWE-295
Type Values Removed Values Added
Weaknesses CWE-295
Type Values Removed Values Added
Weaknesses CWE-295
Type Values Removed Values Added
Weaknesses CWE-295
Type Values Removed Values Added
Weaknesses CWE-287
Type Values Removed Values Added
Weaknesses CWE-287
Type Values Removed Values Added
First Time appeared Curl
Curl curl
Vendors & Products Curl
Curl curl
Type Values Removed Values Added
Description When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key type already recorded for that host in the `known_hosts` file. Instead of rejecting the mismatch, the callback mechanism fails to properly enforce the restriction, allowing the connection to succeed without warning and risking a potential man-in-the-middle attack.
Title SSH improper host validation
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
curl
Published
Updated
Sep 15, 2026, 6:03 AM
Reserved
May 26, 2026, 6:45 AM
Status
Modified
Published
Jul 3, 2026, 7:16 AM
Modified
Sep 15, 2026, 7:16 AM
Severity
Important
Public date
Jul 3, 2026, 6:18 AM