Yes. Go 1.4 reached end of life on 17 February 2016 (10.7 years ago) and no longer receives security updates.
- Released
- 10 December 2014
- Security support ends
- 17 February 2016
- Latest release
- 1.4.3 · 23 September 2015
- Long-term support
- No
What this means for your servers
New vulnerabilities in Go 1.4 are no longer fixed. Every newly published CVE that affects it stays open on your servers, and vulnerability scanners and compliance audits (PCI DSS, SOC 2, Cyber Essentials, ISO 27001) flag unsupported software as a finding. Upgrade, or isolate the machine until you can.
How to check if you’re running Go 1.4
CLI
go version
# for a compiled binary:
go version ./yourbinaryWhat to upgrade to
The newest supported release is Go 1.27.
Only the two most recent Go releases get security fixes, so plan to upgrade every six months. Go keeps backward compatibility, so upgrading is usually just installing the new toolchain (or raising the go/toolchain line in go.mod) and rebuilding. Binaries built with an old Go version keep its vulnerabilities until you rebuild.
Find end-of-life software before an auditor does
Statance reads the version from official Go container image tags on your servers and raises a security finding when it goes past end of life or falls behind the latest patch, along with known CVEs from OSV.dev and CISA’s Known Exploited Vulnerabilities list. Security monitoring is included in Pro and Business. How security monitoring works.
Other Go releases
| Release | Status | Security support ends |
|---|---|---|
| Go 1.27 | Supported | No date announced |
| Go 1.26 | Supported | No date announced |
| Go 1.7 | End of life | 24 August 2017 |
| Go 1.6 | End of life | 16 February 2017 |
| Go 1.5 | End of life | 15 August 2016 |
| Go 1.3 | End of life | 19 August 2015 |
| Go 1.2 | End of life | 10 December 2014 |
FAQ
Is Go 1.4 end of life?
Yes. Go 1.4 reached end of life on 17 February 2016 (10.7 years ago) and no longer receives security updates.
When does Go 1.4 reach end of life?
Security support for Go 1.4 ended on 17 February 2016.
What should I upgrade Go 1.4 to?
Go 1.27 is the newest release that is still supported. Only the two most recent Go releases get security fixes, so plan to upgrade every six months.
Can I keep running Go 1.4 after end of life?
It keeps working, but new vulnerabilities will not be fixed, so every newly published CVE stays open on your server. Scanners and compliance frameworks (PCI DSS, SOC 2, Cyber Essentials) treat unsupported software as a finding.
What is the latest version of Go 1.4?
The latest release in this cycle is 1.4.3, released on 23 September 2015.
Lifecycle data from endoflife.date/go, refreshed 17 November 2026. Vendors occasionally change dates; check the vendor’s own lifecycle page before making a compliance decision.
Stop tracking end-of-life dates by hand.
Statance flags end-of-life and vulnerable software on every server automatically.