CVE-2026-7598

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory published 2026-05-02. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
7.3EG
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.3Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A security vulnerability has been detected in libssh2 up to 1.11.1. The impacted element is the function userauth_password of the file src/userauth.c. Such manipulation of the argument username_len/password_len leads to integer overflow. The attack may be launched remotely. The name of the patch is 256d04b60d80bf1190e96b0ad1e91b2174d744b1. A patch should be applied to remediate this issue.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
64(Attend)
EG Risk 64/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
Severity73% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

May 1, 2026

Last Modified

July 15, 2026

Advisory Details (3)

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

userauth.c: username_len bounds checking by willco007 · Pull Request #1858 · libssh2/libssh2 · GitHub

https://github.com/libssh2/libssh2/pull/1858
generic

userauth.c: username_len bounds checking (#1858) · libssh2/libssh2@256d04b · GitHub

https://github.com/libssh2/libssh2/commit/256d04b60d80bf1190e96b0ad1e91b2174d744b1
generic

GitHub - libssh2/libssh2: the SSH library · GitHub

https://github.com/libssh2/libssh2/

Vendor Advisories for CVE-2026-7598(4)

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.1) @ resolute2026-08-23ubuntu
redhatrust-main-1.95.0-5.hum12026-05-13redhat
redhatlibssh2-main-1.11.1-5.1.hum12026-04-08redhat

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

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
libssh2—1.11.0-r3—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
libssh2—1.11.1-r1—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
libssh2—1.11.1-r1—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
libssh2—1.11.1-r2—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
libssh2—1.11.1-r2—
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-3 ... 1.11.1-5 (15 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libssh21.11.1-11.11.1-1+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libssh21.11.1-1, 1.11.1-21.11.1-3—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

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 / 94× 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 229 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-7598?
CVE-2026-7598 is a high vulnerability published on May 1, 2026. A security vulnerability has been detected in libssh2 up to 1.11.1. The impacted element is the function userauthpassword of the file src/userauth.c. Such manipulation of the argument usernamelen/password_len leads to integer overflow. The attack may be launched remotely. The name of the patch is…
When was CVE-2026-7598 disclosed?
CVE-2026-7598 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7598 actively exploited?
CVE-2026-7598 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 61.7% of all scored CVEs.
What is the CVSS score of CVE-2026-7598?
CVE-2026-7598 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-7598?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7598, 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-7598

Explore →

Is Your Infrastructure Affected by CVE-2026-7598?

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

Start Free Scan →Browse All CVEs