CVE-2025-8277

LOWPre-NVD 3.13.1—
EchelonGraph scoreMEDIUM confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2025-09-09. A secondary CVSS source baseline 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
3.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 3.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in libssh's handling of key exchange (KEX) processes when a client repeatedly sends incorrect KEX guesses. The library fails to free memory during these rekey operations, which can gradually exhaust system memory. This issue can lead to crashes on the client side, particularly when using libgcrypt, which impacts application stability and availability.

CVSS v3
3.1
EG Score
3.1LOWmedium confidence
EG Risk
14
EG Risk 14/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 (value × EchelonGraph’s weight)
Severity31% × 45%
The EG Score, 3.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

September 9, 2025

Last Modified

September 1, 2026

References (4)

Vendor Advisories for CVE-2025-8277(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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibssh-gcrypt-dev (0.9.3-2ubuntu2.5+esm3) @ focal2026-09-01ubuntu
ubuntulibssh-doc (0.11.2-1ubuntu0.2) @ questing2026-09-01ubuntu
redhatlibssh-0:0.10.4-18.el92026-05-19redhat

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 rangeFix by version rangeDependents
libssh0.9.5-1 ... 0.9.8-0+deb11u1 (6 versions)
  • every version up to 0.9.8-0+deb11u2: fixed in 0.9.8-0+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libssh0.10.5-2, 0.10.5-3, 0.10.5-3+hurd.1, 0.10.6-0+deb12u1
  • every version up to 0.10.6-0+deb12u2: fixed in 0.10.6-0+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libssh0.11.2-1
  • every version up to 0.11.2-1+deb13u1: fixed in 0.11.2-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libssh0.11.2-1
  • every version up to 0.11.3-1: fixed in 0.11.3-1
—

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 12× in last 7d / 29× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 95 of 202 refreshes on record for this CVE.

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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 107 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-8277?
CVE-2025-8277 is a low-severity vulnerability; its CVE record was published on September 9, 2025. A flaw was found in libssh's handling of key exchange (KEX) processes when a client repeatedly sends incorrect KEX guesses. The library fails to free memory during these rekey operations, which can gradually exhaust system memory. This issue can lead to crashes on the client side, particularly when…
When was CVE-2025-8277 made public?
CVE-2025-8277 was made public on September 9, 2025: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on September 9, 2025. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2025-8277 actively exploited?
CVE-2025-8277 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-8277?
CVE-2025-8277 has a CVSS base score of 3.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-8277?
A fix for CVE-2025-8277 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-8277 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-2025-8277

Explore →

Is Your Infrastructure Affected by CVE-2025-8277?

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

Book a Demo →Browse All CVEs