CVE-2026-3731

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

A weakness has been identified in libssh up to 0.11.3. The impacted element is the function sftp_extensions_get_name/sftp_extensions_get_data of the file src/sftp.c of the component SFTP Extension Name Handler. Executing a manipulation of the argument idx can lead to out-of-bounds read. The attack may be performed from remote. Upgrading to version 0.11.4 and 0.12.0 is sufficient to resolve this issue. This patch is called 855a0853ad3abd4a6cd85ce06fce6d8d4c7a0b60. You should upgrade the affected component.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

March 8, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic
https://www.libssh.org/security/advisories/libssh-2026-sftp-extensions.txt
generic
https://www.libssh.org/files/0.12/libssh-0.12.0.tar.xz
generic

sftp: Fix out-of-bound read from sftp extensions (855a0853) · Commits · libssh project / libssh-mirror · GitLab

https://gitlab.com/libssh/libssh-mirror/-/commit/855a0853ad3abd4a6cd85ce06fce6d8d4c7a0b60

Vendor Advisories for CVE-2026-3731(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibssh-gcrypt-dev (0.9.3-2ubuntu2.5+esm4) @ focal2026-07-27ubuntu
redhatlibssh-main-0.12.0-1.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libssh0.10.4-1 ... 0.9.8-0+deb11u2 (25 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libssh0.10.5-2 ... 0.12.2-1 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libssh0.11.2-1, 0.11.2-1+deb13u1, 0.11.3-10.11.5-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libssh0.11.2-1, 0.11.3-10.12.0-1—

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 8× 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.

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

Frequently asked(5)

What is CVE-2026-3731?
CVE-2026-3731 is a high vulnerability published on March 8, 2026. A weakness has been identified in libssh up to 0.11.3. The impacted element is the function sftpextensionsgetname/sftpextensionsgetdata of the file src/sftp.c of the component SFTP Extension Name Handler. Executing a manipulation of the argument idx can lead to out-of-bounds read. The attack may be…
When was CVE-2026-3731 disclosed?
CVE-2026-3731 was first published in the National Vulnerability Database on March 8, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3731 actively exploited?
CVE-2026-3731 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.2% of all scored CVEs.
What is the CVSS score of CVE-2026-3731?
CVE-2026-3731 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-3731?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3731, 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-3731

Explore →

Is Your Infrastructure Affected by CVE-2026-3731?

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

Start Free Scan →Browse All CVEs