CVE Vulnerabilities

CVE-2026-12064

Improper Validation of Certificate with Host Mismatch

Published: Jul 03, 2026 | Modified: Sep 15, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Ubuntu
LOW
root.io logo minimus.io logo echo.ai logo

When a user invokes curl using a schemeless URL combined with --proto-default sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical SSH security options like CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the libcurl runtime successfully honors CURLOPT_DEFAULT_PROTOCOL and establishes the connection via SFTP/SCP as specified. Because the tool layer skipped the security configuration, these SSH host verification options are silently omitted, causing curl to connect to an unverified SSH remote host without throwing an error.

Weakness

The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.

Affected Software

NameVendorStart VersionEnd Version
CurlHaxx7.81.0 (including)8.21.0 (excluding)
Red Hat Enterprise Linux 10RedHatcurl-0:8.12.1-4.el10_2.3*
Red Hat Enterprise Linux 10.0 Extended Update SupportRedHatcurl-0:8.12.1-1.el10_0.10*
Red Hat Hardened ImagesRedHatcurl-main-8.21.0-0.1.hum1*
Red Hat Hardened ImagesRedHatrust-main-1.96.1-1.hum1*
CurlUbuntudevel*
CurlUbuntuquesting*
CurlUbunturesolute*
CurlUbuntuupstream*

Extended Description

Even if a certificate is well-formed, signed, and follows the chain of trust, it may simply be a valid certificate for a different site than the site that the product is interacting with. In order to ensure data integrity, the certificate must be valid, and it must pertain to the site that is being accessed. Even if the product attempts to check the hostname, it is still possible to incorrectly check the hostname. For example, attackers could create a certificate with a name that begins with a trusted name followed by a NUL byte, which could cause some string-based comparisons to only examine the portion that contains the trusted name.

Potential Mitigations

References