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
Elevated
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.8%CVSS: 7.3Exploit: Elevated riskExposed services: Not assessed

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.3HIGHmedium confidence
EG Risk
64
EG Risk 64/100

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%
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

Published

May 1, 2026

Last Modified

September 1, 2026

Advisory Details (3)

Auto-updated May 1, 2026
Patch available.
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/

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibssh2-1t64 (1.11.0-4.1ubuntu0.24.04.1) @ noble2026-09-01ubuntu
redhatlibssh2-0:1.8.0-4.el7_9.22026-08-31redhat
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 rangeFix by version rangeDependents
libssh2—
  • every version up to 1.11.0-r3: fixed in 1.11.0-r3
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
libssh2—
  • every version up to 1.11.1-r1: fixed in 1.11.1-r1
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
libssh2—
  • every version up to 1.11.1-r1: fixed in 1.11.1-r1
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
libssh2—
  • every version up to 1.11.1-r2: fixed in 1.11.1-r2
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
libssh2—
  • every version up to 1.11.1-r2: fixed in 1.11.1-r2
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libssh21.10.0-1 ... 1.9.0-3 (20 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libssh21.10.0-3
  • every version up to 1.10.0-3+deb12u1: fixed in 1.10.0-3+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libssh21.11.1-1
  • every version up to 1.11.1-1+deb13u1: fixed in 1.11.1-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libssh21.11.1-1, 1.11.1-2
  • every version up to 1.11.1-3: fixed in 1.11.1-3
—

Weakness Classification(2)

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 7× in last 7d / 28× 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 276 total refreshes for this CVE.

  1. 2026-10-10 02:33 UTCOSV refresh
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:13 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:57 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:04 UTCEPSS rescore
  11. 2026-09-29 15:24 UTCEPSS rescore
  12. 2026-09-28 13:52 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-26 00:28 UTCEPSS rescore
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-22 16:01 UTCEPSS rescore
  19. 2026-09-21 21:09 UTCEPSS rescore
  20. 2026-09-20 20:16 UTCEPSS rescore
  21. 2026-09-20 11:51 UTCOSV refresh
  22. 2026-09-18 19:28 UTCEPSS rescore
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-15 03:12 UTCEPSS rescore
Show 75 more
  1. 2026-09-15 03:12 UTCEPSS rescore
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-06 13:48 UTCEPSS rescore
  6. 2026-09-04 05:07 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 13:48 UTCEG score recompute
  10. 2026-09-01 13:48 UTCVendor advisory
  11. 2026-09-01 13:48 UTCGHSA enrichment
  12. 2026-09-01 12:22 UTCEG score recompute
  13. 2026-09-01 12:22 UTCVendor advisory
  14. 2026-09-01 12:22 UTCGHSA enrichment
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-09-01 04:40 UTCEPSS rescore
  17. 2026-08-30 19:18 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:42 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:47 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-24 14:18 UTCEPSS rescore
  25. 2026-08-23 21:43 UTCEG score recompute
  26. 2026-08-23 21:43 UTCVendor advisory
  27. 2026-08-23 21:42 UTCGHSA enrichment
  28. 2026-08-23 00:19 UTCEPSS rescore
  29. 2026-08-21 23:49 UTCEPSS rescore
  30. 2026-08-20 22:56 UTCEPSS rescore
  31. 2026-08-19 17:04 UTCEPSS rescore
  32. 2026-08-18 13:49 UTCEPSS rescore
  33. 2026-08-18 13:49 UTCEPSS rescore
  34. 2026-08-17 13:47 UTCEPSS rescore
  35. 2026-08-17 13:18 UTCEG score recompute
  36. 2026-08-17 13:18 UTCVendor advisory
  37. 2026-08-17 13:18 UTCGHSA enrichment
  38. 2026-08-16 14:56 UTCEPSS rescore
  39. 2026-08-16 14:56 UTCEPSS rescore
  40. 2026-08-16 05:14 UTCEG score recompute
  41. 2026-08-16 05:14 UTCVendor advisory
  42. 2026-08-16 05:14 UTCGHSA enrichment
  43. 2026-08-16 02:15 UTCEPSS rescore
  44. 2026-08-15 02:12 UTCEG score recompute
  45. 2026-08-15 02:12 UTCVendor advisory
  46. 2026-08-15 02:12 UTCGHSA enrichment
  47. 2026-08-15 01:31 UTCEPSS rescore
  48. 2026-08-14 14:58 UTCVendor advisory
  49. 2026-08-14 14:58 UTCGHSA enrichment
  50. 2026-08-14 03:42 UTCEG score recompute
  51. 2026-08-14 03:42 UTCVendor advisory
  52. 2026-08-14 03:42 UTCGHSA enrichment
  53. 2026-08-13 22:00 UTCEPSS rescore
  54. 2026-08-13 04:37 UTCVendor advisory
  55. 2026-08-13 04:37 UTCGHSA enrichment
  56. 2026-08-12 17:22 UTCEG score recompute
  57. 2026-08-12 17:22 UTCVendor advisory
  58. 2026-08-12 17:22 UTCGHSA enrichment
  59. 2026-08-12 13:51 UTCEPSS rescore
  60. 2026-08-11 16:14 UTCEG score recompute
  61. 2026-08-11 16:14 UTCVendor advisory
  62. 2026-08-11 16:14 UTCGHSA enrichment
  63. 2026-08-11 13:43 UTCEPSS rescore
  64. 2026-08-11 01:45 UTCEG score recompute
  65. 2026-08-11 01:45 UTCVendor advisory
  66. 2026-08-11 01:45 UTCGHSA enrichment
  67. 2026-08-11 00:00 UTCEPSS rescore
  68. 2026-08-10 12:45 UTCVendor advisory
  69. 2026-08-10 12:45 UTCGHSA enrichment
  70. 2026-08-10 01:19 UTCVendor advisory
  71. 2026-08-10 01:19 UTCGHSA enrichment
  72. 2026-08-09 14:04 UTCEG score recompute
  73. 2026-08-09 14:04 UTCVendor advisory
  74. 2026-08-09 14:04 UTCGHSA enrichment
  75. 2026-08-09 13:47 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 on May 1, 2026, with the most recent update on September 1, 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.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-7598?
CVE-2026-7598 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-7598?
A fix for CVE-2026-7598 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-7598 are linked in the Vendor Advisories panel on this page.

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.