CVE-2026-5917

CRITICALPre-NVD 8.89.6▲
EchelonGraph scoreMEDIUM confidence

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-12. The CNA's CVSS baseline 8.8; sources differ by 0.8.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 4 sources updated this week
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

libgit2 versions before 1.8.7 and 1.9.0 before 1.9.7 built with the libssh2 SSH backend (USE_SSH=libssh2) contain a shell command injection vulnerability that allows remote attackers to execute arbitrary commands on an SSH server by supplying a repository path containing unescaped shell metacharacters such as single quotes, semicolons, or pipes. The gen_proto() function in ssh_libssh2.c inserts the repository path directly into a shell command string without escaping special characters before passing it to libssh2_channel_exec(), enabling an attacker to craft a malicious submodule URL in a .gitmodules file that, when processed during a recursive clone, causes the remote server's shell to interpret injected commands under the victim's SSH user account.

CVSS v3
8.8
EG Score
9.6CRITICALmedium confidence
EG Risk
44
EG Risk 44/100CISA SSVC

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
Severity96% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.4%
EPSS %ILE
72nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 11, 2026

Last Modified

October 1, 2026

Advisory Details (2)

Auto-updated Aug 23, 2026
Patch available.
generic

libgit2 v0.27.0-v1.9.0 Shell Command Injection via ssh_libssh2 Backend | Advisories | VulnCheck

https://www.vulncheck.com/advisories/libgit2-shell-command-injection-via-ssh-libssh2-backend
generic

GitHub - libgit2/libgit2: A cross-platform, linkable library implementation of Git that you can use in your application. · GitHub

https://github.com/libgit2/libgit2

Vendor Advisories for CVE-2026-5917(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibgit2-dev (0.26.0+dfsg.1-1.1ubuntu0.2+esm3) @ bionic2026-10-05ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libgit21.5.1+ds-1 ... 1.9.7+ds-1 (32 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libgit21.9.0+ds-2
  • every version up to 1.9.0+ds-2+deb13u1: fixed in 1.9.0+ds-2+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libgit21.9.0+ds-2 ... 1.9.6+ds-1 (14 versions)
  • every version up to 1.9.7+ds-1: fixed in 1.9.7+ds-1
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 49× in last 7d / 205× 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 397 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-5917?
CVE-2026-5917 is a critical vulnerability published on August 11, 2026. libgit2 versions before 1.8.7 and 1.9.0 before 1.9.7 built with the libssh2 SSH backend (USESSH=libssh2) contain a shell command injection vulnerability that allows remote attackers to execute arbitrary commands on an SSH server by supplying a repository path containing unescaped shell…
When was CVE-2026-5917 disclosed?
CVE-2026-5917 was first published on August 11, 2026, with the most recent update on October 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-5917 actively exploited?
CVE-2026-5917 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-5917?
CVE-2026-5917 has a CVSS base score of 8.8 (the CNA's own assessment, by vulncheck; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.6 (CRITICAL).
How do I remediate CVE-2026-5917?
A fix for CVE-2026-5917 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-5917 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-5917

Explore →

Is Your Infrastructure Affected by CVE-2026-5917?

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

Book a Demo →Browse All CVEs