Improperly Implemented Security Check for Standard The advisory has been revoked - it doesn't affect any version of package jbcs-httpd24-libcurl-devel  (opens in a new tab)


Threat Intelligence

EPSS
0.41% (36th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-JBCSHTTPD24LIBCURLDEVEL-20663341
  • published9 Oct 2026
  • disclosed3 Jul 2026

Introduced: 3 Jul 2026

CVE-2026-12064  (opens in a new tab)
CWE-358  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jbcs-httpd24-libcurl-devel package and not the jbcs-httpd24-libcurl-devel package as distributed by RHEL.

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.