Server-Side Request Forgery (SSRF) Affecting libcurl4 package, versions <8.14.1-160000.9.1


Severity

Recommended
0.0
low
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.66% (50th 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-20261522
  • published29 Sept 2026
  • disclosed6 Sept 2026

Introduced: 6 Sep 2026

CVE-2026-5773  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade SLES:16.0.0 libcurl4 to version 8.14.1-160000.9.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.

libcurl might in some circumstances reuse the wrong connection for SMB(S) transfers.

libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.

When reusing a connection a range of criteria must be met. Due to a logical error in the code, a network transfer operation that was requested by an application could wrongfully reuse an existing SMB connection to the same server that was using a different "share" than the new subsequent transfer should.

This could in unlucky situations lead to the download of the wrong file or the upload of a file to the wrong place. When this happens, the same credentials are used and the server name is the same.

CVSS Base Scores

version 3.1