CVE-2026-58050

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

libssh2 through 1.11.1 reads an attacker-controlled 32-bit attribute count from a publickey-subsystem response and uses it in the allocation num_attrs * sizeof(libssh2_publickey_attribute) without bounds checking, so on 32-bit platforms the multiplication overflows to an undersized buffer. A malicious SSH server can then drive the attribute-parsing loop to write past the allocation, causing a heap buffer overflow in a connecting libssh2 client.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

June 28, 2026

Last Modified

June 30, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

libssh2 - Integer Overflow in publickey Subsystem Attribute Allocation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/libssh2-integer-overflow-in-publickey-subsystem-attribute-allocation
generic

libssh2/src/publickey.c at master · libssh2/libssh2 · GitHub

https://github.com/libssh2/libssh2/blob/master/src/publickey.c
generic

exploitarium/libssh2-publickey-list-calc-poc at main · bikini/exploitarium · GitHub

https://github.com/bikini/exploitarium/tree/main/libssh2-publickey-list-calc-poc

Vendor Advisories for CVE-2026-58050(3)

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
ubuntulibssh2-1t64 (1.11.1-1ubuntu0.26.04.3) @ resolute2026-09-06ubuntu
redhatlibssh2-0:1.8.0-4.el7_9.22026-08-31redhat
redhatlibssh2-main-1.11.1-10.4.hum12026-08-12redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libssh21.10.0-1 ... 1.9.0-3 (20 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libssh21.10.0-31.10.0-3+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libssh21.11.1-1 ... 1.11.1-6 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libssh21.11.1-1, 1.11.1-2, 1.11.1-3, 1.11.1-4, 1.11.1-51.11.1-6—

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 8× in last 7d / 88× 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 265 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-58050?
CVE-2026-58050 is a high vulnerability published on June 28, 2026. libssh2 through 1.11.1 reads an attacker-controlled 32-bit attribute count from a publickey-subsystem response and uses it in the allocation numattrs * sizeof(libssh2publickey_attribute) without bounds checking, so on 32-bit platforms the multiplication overflows to an undersized buffer. A…
When was CVE-2026-58050 disclosed?
CVE-2026-58050 was first published in the National Vulnerability Database on June 28, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58050 actively exploited?
CVE-2026-58050 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.5% of all scored CVEs.
What is the CVSS score of CVE-2026-58050?
CVE-2026-58050 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-58050?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58050, 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-58050

Explore →

Is Your Infrastructure Affected by CVE-2026-58050?

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

Start Free Scan →Browse All CVEs