Answer in brief
CVE-2026-5773 records a Unknown severity vulnerability in wrong reuse of SMB connection. The current sources do not mark it as known exploited. The current feed maps curl/curl (generic), curl/curl (generic), curl/curl (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps curl/curl (generic), curl/curl (generic), curl/curl (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| curl/curlgeneric | >=7.40.0 <8.14.2 || >=8.15.0 <8.16.1 || >=8.17.0 <8.20.0 | 8.14.2, 8.16.1, 8.20.0 |
| curl/curlgeneric | >=aec2e865f06669b9cb5d26cc1148d70bc418b163 <74a169575d6412dc0ff532acdf94de35a6c2a571 | 74a169575d6412dc0ff532acdf94de35a6c2a571 |
| curl/curlgeneric | 8.19.0 || 8.18.0 || 8.17.0 || 8.16.0 || 8.15.0 || 8.14.1 || 8.14.0 || 8.13.0 || 8.12.1 || 8.12.0 || 8.11.1 || 8.11.0 || 8.10.1 || 8.10.0 || 8.9.1 || 8.9.0 || 8.8.0 || 8.7.1 || 8.7.0 || 8.6.0 || 8.5.0 || 8.4.0 || 8.3.0 || 8.2.1 || 8.2.0 || 8.1.2 || 8.1.1 || 8.1.0 || 8.0.1 || 8.0.0 || 7.88.1 || 7.88.0 || 7.87.0 || 7.86.0 || 7.85.0 || 7.84.0 || 7.83.1 || 7.83.0 || 7.82.0 || 7.81.0 || 7.80.0 || 7.79.1 || 7.79.0 || 7.78.0 || 7.77.0 || 7.76.1 || 7.76.0 || 7.75.0 || 7.74.0 || 7.73.0 || 7.72.0 || 7.71.1 || 7.71.0 || 7.70.0 || 7.69.1 || 7.69.0 || 7.68.0 || 7.67.0 || 7.66.0 || 7.65.3 || 7.65.2 || 7.65.1 || 7.65.0 || 7.64.1 || 7.64.0 || 7.63.0 || 7.62.0 || 7.61.1 || 7.61.0 || 7.60.0 || 7.59.0 || 7.58.0 || 7.57.0 || 7.56.1 || 7.56.0 || 7.55.1 || 7.55.0 || 7.54.1 || 7.54.0 || 7.53.1 || 7.53.0 || 7.52.1 || 7.52.0 || 7.51.0 || 7.50.3 || 7.50.2 || 7.50.1 || 7.50.0 || 7.49.1 || 7.49.0 || 7.48.0 || 7.47.1 || 7.47.0 || 7.46.0 || 7.45.0 || 7.44.0 || 7.43.0 || 7.42.1 || 7.42.0 || 7.41.0 || 7.40.0 | Not reported |
Published upstream
May 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.