CVE-2026-9545 Affecting libcurl4 package, versions <8.14.1-160000.8.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.41% (33rd 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-SLES1600-LIBCURL4-17977679
  • published15 Jul 2026
  • disclosed8 Jul 2026

Introduced: 8 Jul 2026

NewCVE-2026-9545  (opens in a new tab)

How to fix?

Upgrade SLES:16.0.0 libcurl4 to version 8.14.1-160000.8.1 or higher.

NVD Description

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

In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate.

When libcurl returns to the hostname the second time with a cached SSL session (CURLOPT_SSL_SESSIONID_CACHE is not disabled) and early data enabled (the CURLSSLOPT_EARLYDATA bit is set in CURLOPT_SSL_OPTIONS), libcurl might send off the second request's bytes on that new connection before enforcing the certificate verification failure. Potentially leaking sensitive information.

CVSS Base Scores

version 3.1