Public proof of concept

CVE-2017-8386

A public proof of concept exists; no exploitation attested.

Published2017-06-01

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

git-shell in git before 2.4.12, 2.5.x before 2.5.6, 2.6.x before 2.6.7, 2.7.x before 2.7.5, 2.8.x before 2.8.5, 2.9.x before 2.9.4, 2.10.x before 2.10.3, 2.11.x before 2.11.2, and 2.12.x before 2.12.3 might allow remote authenticated users to gain privileges via a repository name that starts with a - (dash) character.

Timeline

dates in UTC

2017-06-0116:29CVE publishedNVD
2026-10-2319:23First public proof of conceptPoC-in-GitHub
2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-8386?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-8386?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Canonical ubuntu linux

Branch	Affected	Fixed in	Source
14.4	= 14.04	no fix published	NVD
16.4	= 16.04	no fix published	NVD
16.10	= 16.10	no fix published	NVD
17.4	= 17.04	no fix published	NVD

Fedoraproject fedora

Branch	Affected	Fixed in	Source
24.x	= 24	no fix published	NVD
25.x	= 25	no fix published	NVD
26.x	= 26	no fix published	NVD

Debian debian linux

Branch	Affected	Fixed in	Source
8.0	= 8.0	no fix published	NVD

2 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

insinuator.netMitigation

Detection

read 2026-10-23 19:23 UTC

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: 1 repository, unverifiedsuz1n/WHS3_vulhub

Sources

NVDCVSS 3.08.8read 2026-10-23
NVDCVSS 2.06.5read 2026-10-23
FIRST EPSSEPSS score12.4 %read 2026-10-23
PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published: 2017-06-01
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2017-8386?

Is CVE-2017-8386 actively exploited?

Active exploitation of CVE-2017-8386 has not been confirmed. Its EPSS score was 12.4% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-8386?

CVE-2017-8386 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database