CVE-2018-6574

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 code build, by leveraging the gcc or clang plugin feature, because -fplugin= and -plugin= arguments were not blocked.

CVSS: 7.8High
Exploited in the wild: Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS: 7.6%chance of exploitation in the next 30 daystop 6% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 7 Feb 2018analysed here 12 Nov 2026

Summary

Triage

Attack surface: Server-side
Exploitable: At runtime
Attack vector: local
Weakness: CWE-94 Code Injection
Can a WAF block it?: No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

golang:go
debian:debian_linux
redhat:enterprise_linux_server
redhat:enterprise_linux_server_aus
redhat:enterprise_linux_server_eus
redhat:enterprise_linux_server_tus

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: remove eval sinks · RASP

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Not listed as of our last sync.
Public exploit code: Unvetted proof-of-concept code on GitHub: 91 GitHub proofs of concept

GitHub proofs of concept

neargle/Go-Get-RCE-CVE-2018-6574-POC24 stars
frozenkp/CVE-2018-65742 stars
wb4r/go-get-rce1 stars
Malone5923/CVE-2018-6574-go-get-RCE1 stars

and 87 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

7 Feb 2018Published
2 Apr 2018First proof-of-concept repository on GitHub (unvetted)53 days later
5 Aug 2024CVE record last updated2,317 days (about 6 years) later
12 Nov 2026Analysed by vulneraibility.com829 days (about 2 years) later

CVSS vector

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

Metric	Value	What it means
Attack vector	LocalLocal access required (shell, logged-in user).	Local access required (shell, logged-in user).
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	LowThe attacker needs basic user privileges.	The attacker needs basic user privileges.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	HighComplete modification possible.	Complete modification possible.
Availability	HighFull outage possible.	Full outage possible.

Common questions

Is CVE-2018-6574 being exploited?

Not confirmed. CVE-2018-6574 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 7.6% probability of exploitation in the next 30 days.

How severe is CVE-2018-6574?

CVE-2018-6574 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2018-6574?

Yes. A fix has been recorded for CVE-2018-6574. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2018-6574 affect?

CVE-2018-6574 affects golang:go, debian:debian_linux, redhat:enterprise_linux_server, redhat:enterprise_linux_server_aus, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

7 references in the CVE record, grouped by the tags the record gives them.

Advisories (3)

access.redhat.com /errata/RHSA-2018:1304
access.redhat.com /errata/RHSA-2018:0878
debian.org /security/2019/dsa-4380

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
FIRST EPSS: exploit probability and percentile
PoC-in-GitHub: GitHub repositories that claim a proof of concept

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.