Comparison Using Wrong Factors Affecting rust-std-static-x86_64-unknown-none package, versions *


Severity

Recommended
0.0
medium
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.03% (9th 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-CENTOS10-RUSTSTDSTATICX8664UNKNOWNNONE-16346673
  • published3 May 2026
  • disclosed29 Apr 2026

Introduced: 29 Apr 2026

NewCVE-2026-5773  (opens in a new tab)
CWE-1025  (opens in a new tab)

How to fix?

There is no fixed version for Centos:10 rust-std-static-x86_64-unknown-none.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-std-static-x86_64-unknown-none package and not the rust-std-static-x86_64-unknown-none package as distributed by Centos. See How to fix? for Centos:10 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