CVE-2018-11235

HIGHNVD 7.88.2▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.2 because EPSS predicts 49% probability of exploitation within the next 30 days (top 1.2% of all CVEs). NVD baseline CVSS 7.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 49%CVSS: 7.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. With a crafted .gitmodules file, a malicious project can execute an arbitrary script on a machine that runs "git clone --recurse-submodules" because submodule "names" are obtained from this file, and then appended to $GIT_DIR/modules, leading to directory traversal with "../" in a name. Finally, post-checkout hooks from a submodule are executed, bypassing the intended design in which hooks are not obtained from a remote server.

CVSS v3
7.8
EG Score
8.2(high)
EG Risk
61(Track)
EG Risk 61/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
Severity82% × 45%
Exploitation49% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
49%
EPSS %ILE
99%
KEV
Not listed

Published

May 30, 2018

Last Modified

November 21, 2024

Advisory Details (7)

Auto-updated Sep 22, 2026
🔬 Proof of concept available. Patch available. Sources: redhat.
generic

[SECURITY] [DSA 4212-1] git security update

https://www.debian.org/security/2018/dsa-4212
generic

Git: Multiple vulnerabilities (GLSA 201805-13) — Gentoo security

https://security.gentoo.org/glsa/201805-13
generic🟡 PoC Available

'[ANNOUNCE] Git v2.17.1, v2.13.7, v2.14.4, v2.15.2 and v2.16.4' - MARC

https://marc.info/?l=git&m=152761328506724&w=2
generic

Remediating the May 2018 Git Security Vulnerability - Azure DevOps Blog

https://blogs.msdn.microsoft.com/devops/2018/05/29/announcing-the-may-2018-git-security-vulnerability/
redhat Patch Available
https://access.redhat.com/errata/RHSA-2018:2147
redhat Patch Available

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2018:1957
generic

CVE-2018-11235 - PSIRT.COM

http://www.securityfocus.com/bid/104345

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntugitweb (1:2.7.4-0ubuntu1.4) @ xenial2026-05-28ubuntu
redhatrh-git29-git-0:2.9.3-4.el72018-07-10redhat
redhatgit-0:1.8.3.1-14.el7_52018-06-21redhat

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

(26 across 26 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.11(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.5(1)
PackageVulnerable rangeFixed inDependents
git—2.11.3-r1—
Alpine:v3.6(1)
PackageVulnerable rangeFixed inDependents
git—2.13.7—
Alpine:v3.7(1)
PackageVulnerable rangeFixed inDependents
git—2.15.2-r0—
Alpine:v3.8(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Alpine:v3.9(1)
PackageVulnerable rangeFixed inDependents
git—2.17.1-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
git—1:2.17.1-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
git—1:2.17.1-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
git—1:2.17.1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
git—1:2.17.1-1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
git1:2.1.4-2.1 ... 1:2.1.4-2.1+deb8u5 (6 versions)1:2.1.4-2.1+deb8u6—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
git1:2.11.0-3, 1:2.11.0-3+deb9u1, 1:2.11.0-3+deb9u21:2.11.0-3+deb9u3—

Weakness Classification(1)

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

All Vendor Advisories

(3)

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 5× in last 7d / 24× 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 131 total refreshes for this CVE.

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

Publicly available exploits

(4 references)

Working exploit code is in the public domain (4 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCj4k0m/CVE-2018-11235
    First seen Sep 22, 2021

    Auto malicious git repository creation to exploit CVE-2018-11235 a Remote Code Execution using Git Sub module.

    Open source ↗
  • GitHub PoCqweraqq/CVE-2018-11235-Git-Submodule-CE
    First seen Apr 9, 2019

    CVE-2018-11235-Git PoC

    Open source ↗
  • GitHub PoCCHYbeta/CVE-2018-11235-DEMO
    First seen Jun 1, 2018
    Open source ↗
  • GitHub PoCRogdham/CVE-2018-11235
    First seen May 30, 2018

    PoC exploit for CVE-2018-11235 allowing RCE on git clone --recurse-submodules

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

redhat:RHSA-2018:2147

Frequently asked(5)

What is CVE-2018-11235?
CVE-2018-11235 is a high vulnerability published on May 30, 2018. In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. With a crafted .gitmodules file, a malicious project can execute an arbitrary script on a machine that runs "git clone --recurse-submodules" because…
When was CVE-2018-11235 disclosed?
CVE-2018-11235 was first published in the National Vulnerability Database on May 30, 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-11235 actively exploited?
CVE-2018-11235 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 49% probability of exploitation in the next 30 days, which ranks it in the top 1.2% of all scored CVEs.
What is the CVSS score of CVE-2018-11235?
CVE-2018-11235 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.2.
How do I remediate CVE-2018-11235?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-11235, 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-2018-11235

Explore →

Is Your Infrastructure Affected by CVE-2018-11235?

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

Book a Demo →Browse All CVEs