Improper Certificate Validation Affecting libcurl package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.01% (2nd 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-RHEL7-LIBCURL-15979187
  • published11 Apr 2026
  • disclosed7 Jan 2026

Introduced: 7 Jan 2026

CVE-2025-13034  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 libcurl.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

When using CURLOPT_PINNEDPUBLICKEY option with libcurl or --pinnedpubkey with the curl tool,curl should check the public key of the server certificate to verify the peer.

This check was skipped in a certain condition that would then make curl allow the connection without performing the proper check, thus not noticing a possible impostor. To skip this check, the connection had to be done with QUIC with ngtcp2 built to use GnuTLS and the user had to explicitly disable the standard certificate verification.

CVSS Base Scores

version 3.1