CVE-2026-7598

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.3 from GitHub Security Advisory (severity: MODERATE) published 2026-05-02. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-26722 (ENISA EUVD) · GHSA-jhp3-h4hp-2c3p (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.3Exploit: No code on recordExposed 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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 1, 2026

Last Modified

November 11, 2026

Advisory Details (3)

Auto-updated May 1, 2026
Patch available.
Web page

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

https://github.com/libssh2/libssh2/pull/1858
Web page

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

https://github.com/libssh2/libssh2/commit/256d04b60d80bf1190e96b0ad1e91b2174d744b1
Web page

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.1-1ubuntu0.26.04.1) @ resolute2026-11-11ubuntu
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

(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 17× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 342 rows on record for this CVE, as 98 entries (2 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 242 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-11-11 23:32 UTCEchelonGraph re-scored
  3. 2026-11-11 23:32 UTCVendor advisory
  4. 2026-11-11 23:32 UTCGHSA enrichmentGHSA-jhp3-h4hp-2c3p · GitHub severity MODERATE · GitHub CVSS 7.3
  5. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  6. 2026-11-11 03:58 UTCEchelonGraph re-scored
  7. 2026-11-11 03:58 UTCVendor advisory
  8. 2026-11-11 03:58 UTCGHSA enrichmentGHSA-jhp3-h4hp-2c3p · GitHub severity MODERATE · GitHub CVSS 7.3
  9. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-11-10 13:28 UTCEchelonGraph re-scored
  11. 2026-11-10 13:28 UTCVendor advisory
  12. 2026-11-10 13:28 UTCGHSA enrichmentGHSA-jhp3-h4hp-2c3p · GitHub severity MODERATE · GitHub CVSS 7.3
  13. 2026-11-10 12:45 UTCEchelonGraph re-scored
  14. 2026-11-10 12:45 UTCVendor advisory
  15. 2026-11-10 12:45 UTCGHSA enrichmentGHSA-jhp3-h4hp-2c3p · GitHub severity MODERATE · GitHub CVSS 7.3
  16. 2026-11-09 17:56 UTCEchelonGraph re-scored
  17. 2026-11-09 17:56 UTCVendor advisory
  18. 2026-11-09 17:56 UTCGHSA enrichmentGHSA-jhp3-h4hp-2c3p · GitHub severity MODERATE · GitHub CVSS 7.3
  19. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 73 more
  1. 2026-11-03 05:50 UTCEchelonGraph re-scored
  2. 2026-11-03 05:50 UTCVendor advisory
  3. 2026-11-03 05:50 UTCGHSA enrichmentGHSA-jhp3-h4hp-2c3p · GitHub severity MODERATE · GitHub CVSS 7.3
  4. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-27 17:43 UTCEchelonGraph re-scored
  10. 2026-10-27 17:43 UTCVendor advisory
  11. 2026-10-27 17:43 UTCGHSA enrichmentGHSA-jhp3-h4hp-2c3p · GitHub CVSS 7.3
  12. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-25 14:02 UTCEchelonGraph re-scored
  16. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  17. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  18. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  19. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  20. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  21. 2026-10-19 19:21 UTCEchelonGraph re-scored
  22. 2026-10-19 19:21 UTCVendor advisory
  23. 2026-10-19 19:21 UTCGHSA enrichmentGHSA-jhp3-h4hp-2c3p · GitHub CVSS 7.3
  24. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  25. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  26. 2026-10-18 03:13 UTCEchelonGraph re-scored
  27. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  28. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  29. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  30. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  31. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  32. 2026-10-13 07:15 UTCEchelonGraph re-scored
  33. 2026-10-13 07:15 UTCVendor advisory
  34. 2026-10-13 07:14 UTCGHSA enrichmentGHSA-jhp3-h4hp-2c3p · GitHub CVSS 7.3
  35. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  36. 2026-10-12 15:38 UTCEchelonGraph re-scored
  37. 2026-10-11 19:24 UTCEchelonGraph re-scored
  38. 2026-10-11 16:40 UTCEchelonGraph re-scored
  39. 2026-10-11 13:59 UTCEchelonGraph re-scored
  40. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  41. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  42. 2026-10-10 02:33 UTCOSV refresh
  43. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  44. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  45. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  46. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  47. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  48. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  49. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  50. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  51. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  52. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  53. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  54. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  55. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  56. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  57. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  58. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  59. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  60. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  61. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  62. 2026-09-20 11:51 UTCOSV refresh
  63. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  64. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  65. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  66. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  67. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  68. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  69. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  70. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  71. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  72. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  73. 2026-09-01 13:48 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-7598?
CVE-2026-7598 is a high-severity vulnerability; its CVE record was published on May 1, 2026. 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…
When was the CVE record for CVE-2026-7598 published?
The CVE record for CVE-2026-7598 was published on May 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 11, 2026; the record at its source may have been updated since.
Is CVE-2026-7598 actively exploited?
CVE-2026-7598 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd 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.