CVE Watchtower

CVE-2026-5917libgit2 OS Command Injection

NVD

Vulnerability Summary

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.
Severity Level
HIGH(8.6)
Published Date
Aug 11, 2026
Last Modified
Oct 1, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
1.43%Probability
Root Weakness (CWE)
The software constructs all or part of an OS command using externally-influenced input, but does not properly neutralize special elements.
CVSS v4.0 Base Metrics — Score 8.6 (HIGH)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsNone
Privileges RequiredNone
User InteractionActive
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)High
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None
Show CVSS v3.x metrics (score 8.8)
CVSS v3.1 Base Metrics — Score 8.8 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

Affected & Patched Versions

Affected Versions
  • libgit2 < 1.8.7
  • libgit2 >= 1.9.0 and < 1.9.7
Patched Versions
  • libgit2 1.8.7
  • libgit2 1.9.7

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run libgit2 and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Aug 11, 2026Published
  • Oct 1, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new libgit2 CVEsYou are reading CVE-2026-5917. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More libgit2 CVEs

Data last checked: Nov 17, 2026 23:14 UTC