Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2018-16873: 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…

HighCVSS 8.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 52/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 66.2% (FIRST EPSS); higher than 99.2% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: golang-1.7 (Debian:9) 1.7.4-2+deb9u3; golang-1.8 (Debian:9) 1.8.1-1+deb9u3; toolchain (Go) 1.11.3, 1.10.6.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to golang-1.7 (Debian:9) 1.7.4-2+deb9u3; golang-1.8 (Debian:9) 1.8.1-1+deb9u3; toolchain (Go) 1.11.3, 1.10.6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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".

Published
Dec 14, 2018
Updated
Jun 16, 2026
EPSS
66.2% · 99th percentile

Report tools

JSON

Action score

52

Plan

Add it to your regular patch cycle.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
20 / 30 · 66.2%

CNA vs NVD score

NVD
8.1
CNA · redhat
7.5
0.6 point gap

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2018-16873

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
golanggo
opensusebackports sle
opensuseleap
suselinux enterprise server
debiandebian linux

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • [UNKNOWN] golang

    • 1.10.6, 1.11.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:9golang-1.7before 1.7.4-2+deb9u31.7.4-2+deb9u3
Debian:9golang-1.8before 1.8.1-1+deb9u31.8.1-1+deb9u3
Gotoolchainfrom 1.11.0-0 · before 1.11.31.11.3
Gotoolchainbefore 1.10.61.10.6
openSUSE:Leap 15.0containerdbefore 1.2.5-lp150.4.14.31.2.5-lp150.4.14.3
openSUSE:Leap 15.0dockerbefore 18.09.6_ce-lp150.5.17.218.09.6_ce-lp150.5.17.2
openSUSE:Leap 15.0docker-runcbefore 1.0.0rc6+gitr3804_2b18fe1d885e-lp150.5.21.21.0.0rc6+gitr3804_2b18fe1d885e-lp150.5.21.2
openSUSE:Leap 15.0gobefore 1.12-lp150.2.11.11.12-lp150.2.11.1
openSUSE:Leap 15.0go1.11before 1.11.9-lp150.9.31.11.9-lp150.9.3
openSUSE:Leap 15.0go1.12before 1.12.4-lp150.2.21.12.4-lp150.2.2
openSUSE:Leap 15.0golang-github-docker-libnetworkbefore 0.7.0.1+gitr2726_872f0a83c98a-lp150.3.14.10.7.0.1+gitr2726_872f0a83c98a-lp150.3.14.1
openSUSE:Leap 15.1containerdbefore 1.2.5-lp151.2.3.11.2.5-lp151.2.3.1
openSUSE:Leap 15.1cri-obefore 1.17.1-lp151.2.21.17.1-lp151.2.2
openSUSE:Leap 15.1cri-toolsbefore 1.18.0-lp151.2.11.18.0-lp151.2.1
openSUSE:Leap 15.1dockerbefore 18.09.6_ce-lp151.2.3.118.09.6_ce-lp151.2.3.1
openSUSE:Leap 15.1docker-runcbefore 1.0.0rc6+gitr3804_2b18fe1d885e-lp151.3.3.11.0.0rc6+gitr3804_2b18fe1d885e-lp151.3.3.1
openSUSE:Leap 15.1gobefore 1.12-lp151.2.3.11.12-lp151.2.3.1
openSUSE:Leap 15.1go1.11before 1.11.9-lp151.2.3.11.11.9-lp151.2.3.1
openSUSE:Leap 15.1go1.12before 1.12.4-lp151.2.3.11.12.4-lp151.2.3.1
openSUSE:Leap 15.1go1.14before 1.14-lp151.6.11.14-lp151.6.1
openSUSE:Leap 15.1golang-github-docker-libnetworkbefore 0.7.0.1+gitr2726_872f0a83c98a-lp151.2.3.10.7.0.1+gitr2726_872f0a83c98a-lp151.2.3.1
openSUSE:Leap 15.1kubernetesbefore 1.18.0-lp151.5.11.18.0-lp151.5.1
openSUSE:Leap 15.5etcdbefore 3.5.12-150000.7.6.13.5.12-150000.7.6.1
openSUSE:Tumbleweedcontainerdbefore 1.4.8-2.21.4.8-2.2

+43

Other highest-scoring records for the same primary product.

  • CVE-2018-7187The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only…
    54Plan
  • CVE-2021-38297Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when…
    42Plan
  • CVE-2019-14809net/url in Go before 1.11.13 and 1.12.x before 1.12.8 mishandles malformed hosts in URLs, leading to an authorization bypass in some…
    42Plan

Published before and after this one in the same product

  • ← EarlierCVE-2015-5740Oct 18, 2017 · The net/http library in net/http/transfer.go in Go before 1.4.3 does not properly parse HTTP headers, which allows remote attackers to…
    40Plan
  • ← EarlierCVE-2018-6574Feb 7, 2018 · Go before 1.8.7, Go 1.9.x before 1.9.4, and Go 1.10 pre-releases before Go 1.10rc2 allow "go get" remote command execution during source…
    33Monitor
  • Later →CVE-2018-16874Dec 14, 2018 · In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to directory traversal when executed with the import path…
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:golang-1.71.7.4-2+deb9u3 · Debian:9Package registry (OSV)
debian:golang-1.81.8.1-1+deb9u3 · Debian:9Package registry (OSV)
Go:toolchain1.10.6Package registry (OSV)
Go:toolchain1.11.3Package registry (OSV)
opensuse:containerd1.2.5-lp151.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:cri-o1.17.1-lp151.2.2 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:cri-tools1.18.0-lp151.2.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:docker18.09.6_ce-lp151.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:docker-runc1.0.0rc6+gitr3804_2b18fe1d885e-lp151.3.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:etcd3.5.12-150000.7.6.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:go1.12-lp151.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:go1.111.11.9-lp151.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:go1.121.12.4-lp151.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:go1.141.14-lp151.6.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:golang-github-docker-libnetwork0.7.0.1+gitr2726_872f0a83c98a-lp151.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:kubernetes1.18.0-lp151.5.1 · openSUSE:Leap 15.1Package registry (OSV)
suse:containerd1.1.2-5.3.4 · SUSE:Linux Enterprise Module for Containers 15Package registry (OSV)
suse:docker18.06.1_ce-6.8.2 · SUSE:Linux Enterprise Module for Containers 15Package registry (OSV)
suse:docker-runc1.0.0rc5+gitr3562_69663f0bd4b6-6.3.4 · SUSE:Linux Enterprise Module for Containers 15Package registry (OSV)
suse:go1.12-bp150.2.6.1 · SUSE:Package Hub 15Package registry (OSV)
suse:golang-github-docker-libnetwork0.7.0.1+gitr2664_3ac297bc7fd0-4.3.5 · SUSE:Linux Enterprise Module for Containers 15Package registry (OSV)
suse:helm2.13.1-5.1 · SUSE:Package Hub 12 SP3Package registry (OSV)
suse:helm-mirror0.2.1-1.7.1 · SUSE:Linux Enterprise Module for Containers 15Package registry (OSV)
suse:runc1.0.0~rc93-16.8.1 · SUSE:Linux Enterprise Module for Containers 12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

References

All records