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.
References
| Link | Resource |
|---|---|
| https://curl.se/docs/CVE-2026-5773.html | Patch Vendor Advisory |
| https://curl.se/docs/CVE-2026-5773.json | Vendor Advisory |
| https://hackerone.com/reports/3650689 | Exploit Issue Tracking Third Party Advisory |
| http://www.openwall.com/lists/oss-security/2026/04/29/9 | Mailing List Patch Third Party Advisory |
| https://hackerone.com/reports/3650689 | Exploit Issue Tracking Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-05-13 13:01
Updated : 2026-09-15 07:16
NVD link : CVE-2026-5773
Mitre link : CVE-2026-5773
CVE.ORG link : CVE-2026-5773
JSON object : View
Products Affected
haxx
- curl
