CVE-2026-5773

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-13. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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 v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

May 13, 2026

Last Modified

May 13, 2026

Advisory Details (4)

Auto-updated May 13, 2026
No patch confirmed yet.
generic

HackerOne

https://hackerone.com/reports/3650689
generic

oss-security - [ADVISORY] curl: CVE-2026-5773: wrong reuse of SMB connection

http://www.openwall.com/lists/oss-security/2026/04/29/9
generic
https://curl.se/docs/CVE-2026-5773.json
generic

curl - wrong reuse of SMB connection - CVE-2026-5773

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

Vendor Advisories for CVE-2026-5773(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4t64 (8.18.0-1ubuntu2.1) @ resolute2026-08-23ubuntu
ubuntulibcurl4t64 (8.18.0-1ubuntu2.3) @ resolute2026-08-23ubuntu
redhatcurl-main-8.20.0-0.1.hum12026-05-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
curl—8.20.0-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
curl—8.20.0-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
curl7.74.0-1.3 ... 8.9.1-2~bpo12+1 (219 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
curl7.88.1-10 ... 7.88.1-10+deb12u9 (18 versions)7.88.1-10+deb12u15—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2, 8.14.1-2+deb13u1, 8.14.1-2+deb13u2, 8.14.1-2+deb13u2~bpo13+1, 8.14.1-2+deb13u38.14.1-2+deb13u4—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.20.0~rc1-1+exp3 (45 versions)8.20.0~rc2-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 93× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 266 total refreshes for this CVE.

  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-23 17:58 UTCEG score recompute
  5. 2026-08-23 17:58 UTCVendor advisory
  6. 2026-08-23 17:58 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 21:33 UTCEG score recompute
  11. 2026-08-20 21:33 UTCVendor advisory
  12. 2026-08-20 21:33 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 10:44 UTCEG score recompute
  17. 2026-08-17 10:44 UTCVendor advisory
  18. 2026-08-17 10:44 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 04:08 UTCEG score recompute
  21. 2026-08-16 04:08 UTCVendor advisory
  22. 2026-08-16 04:08 UTCGHSA enrichment
  23. 2026-08-15 02:06 UTCEG score recompute
  24. 2026-08-15 02:06 UTCVendor advisory
  25. 2026-08-15 02:06 UTCGHSA enrichment
Show 75 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 14:21 UTCVendor advisory
  3. 2026-08-14 14:21 UTCGHSA enrichment
  4. 2026-08-14 02:36 UTCEG score recompute
  5. 2026-08-14 02:36 UTCVendor advisory
  6. 2026-08-14 02:36 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 03:39 UTCVendor advisory
  9. 2026-08-13 03:39 UTCGHSA enrichment
  10. 2026-08-12 15:54 UTCEG score recompute
  11. 2026-08-12 15:54 UTCVendor advisory
  12. 2026-08-12 15:54 UTCGHSA enrichment
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-11 15:30 UTCEG score recompute
  15. 2026-08-11 15:30 UTCVendor advisory
  16. 2026-08-11 15:30 UTCGHSA enrichment
  17. 2026-08-11 01:00 UTCEG score recompute
  18. 2026-08-11 01:00 UTCVendor advisory
  19. 2026-08-11 01:00 UTCGHSA enrichment
  20. 2026-08-11 00:00 UTCEPSS rescore
  21. 2026-08-10 13:14 UTCVendor advisory
  22. 2026-08-10 13:14 UTCGHSA enrichment
  23. 2026-08-10 01:29 UTCEG score recompute
  24. 2026-08-10 01:29 UTCVendor advisory
  25. 2026-08-10 01:29 UTCGHSA enrichment
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-09 13:44 UTCVendor advisory
  28. 2026-08-09 13:43 UTCGHSA enrichment
  29. 2026-08-09 01:58 UTCEG score recompute
  30. 2026-08-09 01:58 UTCVendor advisory
  31. 2026-08-09 01:58 UTCGHSA enrichment
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 08:30 UTCVendor advisory
  34. 2026-08-08 08:30 UTCGHSA enrichment
  35. 2026-08-07 20:45 UTCEG score recompute
  36. 2026-08-07 20:45 UTCVendor advisory
  37. 2026-08-07 20:45 UTCGHSA enrichment
  38. 2026-08-07 08:59 UTCVendor advisory
  39. 2026-08-07 08:59 UTCGHSA enrichment
  40. 2026-08-06 21:14 UTCEG score recompute
  41. 2026-08-06 21:14 UTCVendor advisory
  42. 2026-08-06 21:14 UTCGHSA enrichment
  43. 2026-08-06 13:47 UTCEPSS rescore
  44. 2026-08-06 09:28 UTCVendor advisory
  45. 2026-08-06 09:28 UTCGHSA enrichment
  46. 2026-08-05 21:43 UTCEG score recompute
  47. 2026-08-05 21:43 UTCVendor advisory
  48. 2026-08-05 21:43 UTCGHSA enrichment
  49. 2026-08-05 19:17 UTCEPSS rescore
  50. 2026-08-04 15:10 UTCEPSS rescore
  51. 2026-08-04 10:39 UTCEPSS rescore
  52. 2026-08-03 19:11 UTCEG score recompute
  53. 2026-08-03 19:11 UTCVendor advisory
  54. 2026-08-03 19:11 UTCGHSA enrichment
  55. 2026-08-03 10:36 UTCEPSS rescore
  56. 2026-08-02 21:13 UTCVendor advisory
  57. 2026-08-02 21:13 UTCGHSA enrichment
  58. 2026-08-02 09:27 UTCEG score recompute
  59. 2026-08-02 09:27 UTCVendor advisory
  60. 2026-08-02 09:27 UTCGHSA enrichment
  61. 2026-08-02 02:27 UTCEPSS rescore
  62. 2026-08-01 21:14 UTCEG score recompute
  63. 2026-08-01 21:14 UTCVendor advisory
  64. 2026-08-01 21:14 UTCGHSA enrichment
  65. 2026-08-01 04:16 UTCEPSS rescore
  66. 2026-07-30 16:28 UTCEPSS rescore
  67. 2026-07-30 01:30 UTCEPSS rescore
  68. 2026-07-30 01:30 UTCEPSS rescore
  69. 2026-07-28 15:37 UTCEPSS rescore
  70. 2026-07-27 14:14 UTCEPSS rescore
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-26 14:54 UTCEPSS rescore
  73. 2026-07-25 14:18 UTCEPSS rescore
  74. 2026-07-25 14:18 UTCEPSS rescore
  75. 2026-07-24 14:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-5773?
CVE-2026-5773 is a high vulnerability published on May 13, 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…
When was CVE-2026-5773 disclosed?
CVE-2026-5773 was first published in the National Vulnerability Database on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5773 actively exploited?
CVE-2026-5773 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.9% of all scored CVEs.
What is the CVSS score of CVE-2026-5773?
CVE-2026-5773 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-5773?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5773, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-5773

Explore →

Is Your Infrastructure Affected by CVE-2026-5773?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs