CVE-2026-5773

wrong reuse of SMB connection

HIGH

7.5

CVSS Score

Published: May 13, 2026 at 08:27 AM UTC

Updated: September 15, 2026 at 07:35 AM UTC

1 product affected across 1 vendorCurl

Using curl by curl?

Get instant alerts when new vulnerabilities affect curl - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.5

Exploit prediction

EPSS 0.6%

SSVC

PoC

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Curl · Haxx

95%

7.40.0 ≤ v < 8.14.27.40.0 ≤ v < 8.20.08.15.0 ≤ v < 8.16.18.17.0 ≤ v < 8.20.07.40.0 7.41.0 7.42.0 7.42.1 7.43.0 7.44.0 7.45.0 7.46.0 7.47.0 7.47.1 7.48.0 7.49.0 7.49.1 7.50.0 7.50.1 7.50.2 7.50.3 7.51.0 7.52.0 7.52.1 7.53.0 7.53.1 7.54.0 7.54.1 7.55.0 7.55.1 7.56.0 7.56.1 7.57.0 7.58.0 7.59.0 7.60.0 7.61.0 7.61.1 7.62.0 7.63.0 7.64.0 7.64.1 7.65.0 7.65.1 7.65.2 7.65.3 7.66.0 7.67.0 7.68.0 7.69.0 7.69.1 7.70.0 7.71.0 7.71.1 7.72.0 7.73.0 7.74.0 7.75.0 7.76.0 7.76.1 7.77.0 7.78.0 7.79.0 7.79.1 7.80.0 7.81.0 7.82.0 7.83.0 7.83.1 7.84.0 7.85.0 7.86.0 7.87.0 7.88.0 7.88.1 8.0.0 8.0.1 8.1.0 8.1.1 8.1.2 8.10.0 8.10.1 8.11.0 8.11.1 8.12.0 8.12.1 8.13.0 8.14.0 8.14.1 8.15.0 8.16.0 8.17.0 8.18.0 8.19.0 8.2.0 8.2.1 8.3.0 8.4.0 8.5.0 8.6.0 8.7.0 8.7.1 8.8.0 8.9.0 8.9.1aec2e865f06669b9cb5d26cc1148d70bc418b163

Vendor states this is fixed in 74a169575d6412dc0ff532acdf94de35a6c2a571 (fixed)

Affected range stops below 8.14.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 8.16.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 8.20.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (4)

Vendor Advisory

Source: cverecord

https://curl.se/docs/CVE-2026-5773.json

PatchVendor Advisory

Source: cverecord

https://curl.se/docs/CVE-2026-5773.html

ExploitIssue TrackingThird Party Advisory

Source: cverecord

https://hackerone.com/reports/3650689

Mailing ListPatchThird Party Advisory

Source: af854a3a-2127-422b-91ae-364da2661108

http://www.openwall.com/lists/oss-security/2026/04/29/9

SSVC — Action Prioritization

SSVCPoCAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHCISA-ADP

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: NONE
Availability: NONE

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-918CWE-488

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card