CVE-2026-58050

HIGHNVD 7.57.0
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-06-28. NVD baseline CVSS 7.5; sources differ by 0.5.

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.0(high)
EPSS
25.3%
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(2)

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

Data Freshness Timeline

(refreshed 39× in last 7d / 49× 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.

  1. 2026-07-07 01:44 UTCEG score recompute
  2. 2026-07-07 01:44 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 13:04 UTCEG score recompute
  6. 2026-07-06 13:04 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 00:21 UTCEG score recompute
  10. 2026-07-06 00:21 UTCGHSA enrichment
  11. 2026-07-05 11:39 UTCEG score recompute
  12. 2026-07-05 11:39 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 22:56 UTCEG score recompute
  16. 2026-07-04 22:56 UTCGHSA enrichment
  17. 2026-07-04 10:17 UTCEG score recompute
  18. 2026-07-04 10:16 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 21:35 UTCEG score recompute
  22. 2026-07-03 21:35 UTCGHSA enrichment
  23. 2026-07-03 08:55 UTCEG score recompute
  24. 2026-07-03 08:55 UTCGHSA enrichment
  25. 2026-07-02 20:14 UTCEG score recompute
Show 24 more
  1. 2026-07-02 20:14 UTCGHSA enrichment
  2. 2026-07-02 07:34 UTCEG score recompute
  3. 2026-07-02 07:34 UTCGHSA enrichment
  4. 2026-07-01 18:53 UTCEG score recompute
  5. 2026-07-01 18:53 UTCGHSA enrichment
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-07-01 06:13 UTCEG score recompute
  8. 2026-07-01 06:13 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 20:33 UTCNVD updateCVSS v3 → 7.5
  11. 2026-06-30 17:32 UTCEG score recompute
  12. 2026-06-30 17:32 UTCGHSA enrichment
  13. 2026-06-30 04:52 UTCEG score recompute
  14. 2026-06-30 04:52 UTCGHSA enrichment
  15. 2026-06-29 16:11 UTCEG score recompute
  16. 2026-06-29 16:11 UTCGHSA enrichment
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 03:31 UTCEG score recompute
  19. 2026-06-29 03:30 UTCGHSA enrichment
  20. 2026-06-28 14:50 UTCEG score recompute
  21. 2026-06-28 14:50 UTCGHSA enrichment
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 02:10 UTCEG score recompute
  24. 2026-06-28 02:09 UTCMITRE cvelistV5first tracked

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 25.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58050?
CVE-2026-58050 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.0.
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

Explore the affected products and dependency analysis for 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.