Graylog 1.1 · Version Status
Graylog 1.1 End of Life Date
Graylog 1.1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Graylog 1.1 is past end of life. This version no longer receives security patches. 3890 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 14, 2015
3890 days past EOL
Latest Release
1.1.6
Standard release
Release Date
Jun 4, 2015
Graylog 1.1 series
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.2 |
Jun 4, 2015 |
EOL |
| → 1.1 |
1.1.6 |
Sep 14, 2015 |
EOL |
| 1.2 |
1.2.2 |
Dec 8, 2015 |
EOL |
| 1.3 |
1.3.4 |
Apr 26, 2016 |
EOL |
| 2.0 |
2.0.3 |
Sep 1, 2016 |
EOL |
| 2.1 |
2.1.3 |
Feb 9, 2017 |
EOL |
| 2.2 |
2.2.3 |
Jul 26, 2017 |
EOL |
| 2.3 |
2.3.2 |
Dec 22, 2017 |
EOL |
What does Graylog 1.1 end of life mean?
When Graylog 1.1 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Graylog 1.1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Graylog 1.1 reach end of life?
Graylog 1.1 reached end of life on September 14, 2015. This version is no longer receiving security patches.
Is Graylog 1.1 still supported?
No. Graylog 1.1 reached end of life on September 14, 2015 and is no longer receiving security patches.
What should I upgrade to from Graylog 1.1?
What are the security risks of running Graylog 1.1 past EOL?
When Graylog 1.1 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Graylog should migrate immediately or implement compensating controls.