Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2026-5773

wrong reuse of SMB connection

High7.5EPSS 0.62%
Published
Updated
Reserved
Assigned by
curl

Description

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.

Scores

CVSS scores of CVE-2026-5773, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.62% · top 50% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: poc · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Weakness

Affected products

  • curl · curl

    • affected 7.40.0 – < 8.14.2
    • affected 8.15.0 – < 8.16.1
    • affected 8.17.0 – < 8.20.0
  • curl · curl

    • affected aec2e865f06669b9cb5d26cc1148d70bc418b163 – < 74a169575d6412dc0ff532acdf94de35a6c2a571
  • curl · curl

    • affected 8.19.0
    • affected 8.18.0
    • affected 8.17.0
    • affected 8.16.0
    • affected 8.15.0
    • affected 8.14.1
    • affected 8.14.0
    • affected 8.13.0
    • affected 8.12.1
    • affected 8.12.0
    • affected 8.11.1
    • affected 8.11.0
    • affected 8.10.1
    • affected 8.10.0
    • affected 8.9.1
    • affected 8.9.0
    • affected 8.8.0
    • affected 8.7.1
    • affected 8.7.0
    • affected 8.6.0
    • affected 8.5.0
    • affected 8.4.0
    • affected 8.3.0
    • affected 8.2.1
    • affected 8.2.0
    • affected 8.1.2
    • affected 8.1.1
    • affected 8.1.0
    • affected 8.0.1
    • affected 8.0.0
    • affected 7.88.1
    • affected 7.88.0
    • affected 7.87.0
    • affected 7.86.0
    • affected 7.85.0
    • affected 7.84.0
    • affected 7.83.1
    • affected 7.83.0
    • affected 7.82.0
    • affected 7.81.0
    • and 61 more

References (4)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-5773 badge
[![CVE-2026-5773](https://trackcve.app/badge/CVE-2026-5773.svg)](https://trackcve.app/cve/CVE-2026-5773)

Record last updated .