CVE-2018-17456

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 97%
CISA-KEV: Not listedEPSS: 97%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows remote code execution during processing of a recursive "git clone" of a superproject if a .gitmodules file has a URL field beginning with a '-' character.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
99.9%
KEV
Not listed

Published

October 6, 2018

Last Modified

November 21, 2024

Advisory Details (8)

Auto-updated Jun 22, 2026
Patch available. Sources: redhat, github_commit.
github_commit

commit 1a7fd1fb2998 (git/git)

Fix landed in git/git commit 1a7fd1fb2998 — awaiting tagged release

https://github.com/git/git/commit/1a7fd1fb2998002da6e9ff2ee46e1bdd25ee8404
redhat Patch Available

Affected: Red Hat Enterprise Linux 6.

https://access.redhat.com/errata/RHSA-2020:0316
redhat Patch Available

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2018:3408

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntugitweb (1:1.9.1-1ubuntu0.9) @ trusty2026-05-28ubuntu
redhatgit-0:1.7.1-10.el6_102020-02-03redhat
redhatrh-git29-git-0:2.9.3-8.el72018-11-13redhat
redhatgit-0:1.8.3.1-20.el72018-10-30redhat

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.

Weakness Classification(1)

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

All Vendor Advisories

(4)

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 3× in last 7d / 8× 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-07-21 04:34 UTCOSV refresh
  2. 2026-07-20 17:04 UTCEPSS rescore
  3. 2026-07-20 17:04 UTCEPSS rescore
  4. 2026-07-08 15:11 UTCEPSS rescore
  5. 2026-07-03 23:56 UTCOSV refresh
  6. 2026-06-24 14:02 UTCEPSS rescore
  7. 2026-06-24 14:02 UTCEPSS rescore
  8. 2026-06-23 21:30 UTCEPSS rescore
  9. 2026-06-22 14:23 UTCEPSS rescore
  10. 2026-06-17 17:50 UTCEPSS rescore
  11. 2026-06-17 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-16 17:50 UTCEPSS rescore
  14. 2026-06-15 17:45 UTCEPSS rescore
  15. 2026-06-15 12:13 UTCOSV refresh
  16. 2026-06-13 22:58 UTCEPSS rescore
  17. 2026-06-13 22:58 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-11 13:57 UTCEPSS rescore
  20. 2026-06-10 22:16 UTCEPSS rescore
  21. 2026-06-10 13:19 UTCEPSS rescore
  22. 2026-06-08 14:14 UTCEPSS rescore
  23. 2026-06-08 14:14 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-06 13:45 UTCEPSS rescore
Show 15 more
  1. 2026-06-05 22:45 UTCEPSS rescore
  2. 2026-06-05 22:44 UTCEPSS rescore
  3. 2026-06-05 06:08 UTCEPSS rescore
  4. 2026-06-05 06:08 UTCEPSS rescore
  5. 2026-06-02 20:11 UTCEPSS rescore
  6. 2026-06-02 20:11 UTCEPSS rescore
  7. 2026-06-01 13:49 UTCEPSS rescore
  8. 2026-05-31 00:14 UTCEPSS rescore
  9. 2026-05-31 00:14 UTCEPSS rescore
  10. 2026-05-29 13:41 UTCEPSS rescore
  11. 2026-05-28 13:42 UTCEPSS rescore
  12. 2026-05-28 13:42 UTCEPSS rescore
  13. 2026-05-28 02:25 UTCEG score recompute
  14. 2026-05-28 02:25 UTCVendor advisory
  15. 2026-05-28 02:25 UTCGHSA enrichment

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCAnonymKing/CVE-2018-17456
    First seen Jun 21, 2019

    CVE-2018-17456漏洞复现(PoC+Exp)

    Open source ↗
  • Exploit-DBEDB-45631
    First seen Oct 16, 2018

    Git Submodule - Arbitrary Code Execution

    Open source ↗
  • Exploit-DBEDB-45548
    First seen Oct 5, 2018

    Git Submodule - Arbitrary Code Execution (PoC)

    Open source ↗
  • Metasploitexploit/multi/http/git_submodule_url_exec✓ verified
    First seen Oct 5, 2018

    Malicious Git HTTP Server For CVE-2018-17456

    Open source ↗

Frequently asked(5)

What is CVE-2018-17456?
CVE-2018-17456 is a critical vulnerability published on October 6, 2018. Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows remote code execution during processing of a recursive "git clone" of a superproject if a .gitmodules file has a URL field beginning with a '-' character.
When was CVE-2018-17456 disclosed?
CVE-2018-17456 was first published in the National Vulnerability Database on October 6, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-17456 actively exploited?
CVE-2018-17456 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-17456?
CVE-2018-17456 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-17456?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-17456, 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

Explore the affected products and dependency analysis for CVE-2018-17456

Explore →

Is Your Infrastructure Affected by CVE-2018-17456?

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