CVE-2018-16873

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekElevated
8.1
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 66%
CISA-KEV: Not listedEPSS: 66%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious commands, they will execute on the system running "go get -u".

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
99.2%
KEV
Not listed

Published

December 14, 2018

Last Modified

November 21, 2024

References (24)

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
toolchain—1.11.3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× 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.

  1. 2026-07-22 22:14 UTCEG score recompute
  2. 2026-07-22 14:04 UTCEPSS rescore
  3. 2026-07-21 15:21 UTCEPSS rescore
  4. 2026-07-21 01:17 UTCOSV refresh
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-20 17:04 UTCEPSS rescore
  7. 2026-07-16 16:59 UTCEPSS rescore
  8. 2026-07-16 16:59 UTCEPSS rescore
  9. 2026-07-15 16:55 UTCEPSS rescore
  10. 2026-07-13 22:26 UTCEPSS rescore
  11. 2026-07-13 06:10 UTCEPSS rescore
  12. 2026-07-11 08:24 UTCEPSS rescore
  13. 2026-07-09 19:06 UTCEPSS rescore
  14. 2026-07-07 13:42 UTCEPSS rescore
  15. 2026-07-07 13:42 UTCEPSS rescore
  16. 2026-07-05 02:27 UTCEPSS rescore
  17. 2026-07-03 20:56 UTCOSV refresh
  18. 2026-07-02 16:54 UTCEPSS rescore
  19. 2026-07-01 15:03 UTCEPSS rescore
  20. 2026-07-01 15:03 UTCEPSS rescore
  21. 2026-06-27 03:06 UTCEPSS rescore
  22. 2026-06-25 13:47 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
Show 39 more
  1. 2026-06-21 01:57 UTCEPSS rescore
  2. 2026-06-18 17:50 UTCEPSS rescore
  3. 2026-06-18 17:50 UTCEPSS rescore
  4. 2026-06-17 17:50 UTCEPSS rescore
  5. 2026-06-17 17:50 UTCEPSS rescore
  6. 2026-06-16 17:50 UTCEPSS rescore
  7. 2026-06-16 17:50 UTCEPSS rescore
  8. 2026-06-15 17:45 UTCEPSS rescore
  9. 2026-06-15 08:43 UTCOSV refresh
  10. 2026-06-14 23:14 UTCEPSS rescore
  11. 2026-06-14 23:14 UTCEPSS rescore
  12. 2026-06-12 23:09 UTCEPSS rescore
  13. 2026-06-11 13:57 UTCEPSS rescore
  14. 2026-06-10 22:16 UTCEPSS rescore
  15. 2026-06-10 13:19 UTCEPSS rescore
  16. 2026-06-08 14:14 UTCEPSS rescore
  17. 2026-06-08 14:14 UTCEPSS rescore
  18. 2026-06-05 22:45 UTCEPSS rescore
  19. 2026-06-05 22:44 UTCEPSS rescore
  20. 2026-06-05 06:08 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-04 13:10 UTCEPSS rescore
  23. 2026-06-04 13:10 UTCEPSS rescore
  24. 2026-06-02 20:11 UTCEPSS rescore
  25. 2026-06-02 20:11 UTCEPSS rescore
  26. 2026-06-01 13:49 UTCEPSS rescore
  27. 2026-05-31 22:29 UTCEPSS rescore
  28. 2026-05-31 22:28 UTCEPSS rescore
  29. 2026-05-31 00:14 UTCEPSS rescore
  30. 2026-05-31 00:14 UTCEPSS rescore
  31. 2026-05-29 13:41 UTCEPSS rescore
  32. 2026-05-28 13:42 UTCEPSS rescore
  33. 2026-05-28 13:42 UTCEPSS rescore
  34. 2026-05-28 00:17 UTCEG score recompute
  35. 2026-05-28 00:17 UTCGHSA enrichment
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-26 07:17 UTCEPSS rescore
  39. 2026-05-26 07:17 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-16873?
CVE-2018-16873 is a high vulnerability published on December 14, 2018. In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in…
When was CVE-2018-16873 disclosed?
CVE-2018-16873 was first published in the National Vulnerability Database on December 14, 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-16873 actively exploited?
CVE-2018-16873 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-16873?
CVE-2018-16873 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2018-16873?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-16873, 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-16873

Explore →

Is Your Infrastructure Affected by CVE-2018-16873?

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

Start Free Scan →Browse All CVEs