Graylog End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Graylog versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Graylog 7.1 is supported until May 4, 2027, its end-of-support date. The next Graylog version to reach end of life is 7.0, on November 3, 2026. 25 of 27 tracked Graylog versions are past end of life; the most recent to reach it, 6.3, did so on June 30, 2026. The full Graylog lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.2 | Feb 17, 2015 | Jun 4, 2015 | 4129 days past EOL | EOL |
| 1.1 | 1.1.6 | Jun 4, 2015 | Sep 14, 2015 | 4027 days past EOL | EOL |
| 1.2 | 1.2.2 | Sep 14, 2015 | Dec 8, 2015 | 3942 days past EOL | EOL |
| 1.3 | 1.3.4 | Dec 8, 2015 | Apr 26, 2016 | 3802 days past EOL | EOL |
| 2.0 | 2.0.3 | Apr 26, 2016 | Sep 1, 2016 | 3674 days past EOL | EOL |
| 2.1 | 2.1.3 | Sep 1, 2016 | Feb 9, 2017 | 3513 days past EOL | EOL |
| 2.2 | 2.2.3 | Feb 9, 2017 | Jul 26, 2017 | 3346 days past EOL | EOL |
| 2.3 | 2.3.2 | Jul 26, 2017 | Dec 22, 2017 | 3197 days past EOL | EOL |
| 2.4 | 2.4.7 | Dec 22, 2017 | Mar 1, 2019 | 2763 days past EOL | EOL |
| 2.5 | 2.5.2 | Dec 1, 2018 | Feb 11, 2019 | 2781 days past EOL | EOL |
| 3.0 | 3.0.2 | Feb 11, 2019 | Aug 15, 2019 | 2596 days past EOL | EOL |
| 3.1 | 3.1.4 | Aug 15, 2019 | Jan 31, 2020 | 2427 days past EOL | EOL |
| 3.2 | 3.2.6 | Jan 31, 2020 | May 20, 2020 | 2317 days past EOL | EOL |
| 3.3 | 3.3.17 | May 20, 2020 | Apr 12, 2022 | 1625 days past EOL | EOL |
| 4.0 | 4.0.17 | Nov 17, 2020 | Oct 13, 2021 | 1806 days past EOL | EOL |
| 4.1 | 4.1.14 | Jun 23, 2021 | May 17, 2022 | 1590 days past EOL | EOL |
| 4.2 | 4.2.13 | Oct 13, 2021 | Nov 30, 2022 | 1393 days past EOL | EOL |
| 4.3 | 4.3.15 | May 25, 2022 | May 25, 2023 | 1217 days past EOL | EOL |
| 5.0 | 5.0.13 | Dec 6, 2022 | Dec 6, 2023 | 1022 days past EOL | EOL |
| 5.1 | 5.1.13 | May 17, 2023 | May 17, 2024 | 859 days past EOL | EOL |
| 5.2 | 5.2.12 | Nov 1, 2023 | Nov 1, 2024 | 691 days past EOL | EOL |
| 6.0 | 6.0.14 | May 7, 2024 | May 8, 2025 | 503 days past EOL | EOL |
| 6.1 | 6.1.16 | Oct 20, 2024 | Oct 20, 2025 | 338 days past EOL | EOL |
| 6.2 | 6.2.14 | Apr 28, 2025 | Apr 28, 2026 | 148 days past EOL | EOL |
| 6.3 | 6.3.15 | Jun 30, 2025 | Jun 30, 2026 | 85 days past EOL | EOL |
| 7.0 | 7.0.13 | Nov 3, 2025 | Nov 3, 2026 | 41 days remaining | Warning |
| 7.1 | 7.1.9 | May 4, 2026 | May 4, 2027 | 223 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/graylog)
Graylog release and support pattern
Across the 27 release lines with a published release date, Graylog has shipped a new line roughly every 5 months (median interval). A line typically stays supported for about 0.9 years from its release to its end-of-life date.
Of the 27 release lines tracked, 25 are past end of life and 2 are still within support. The newest line, 7.1, was released May 4, 2026. The next scheduled end of life is 7.0 on November 3, 2026 — 41 days from this build. The longest-supported line currently published is 7.1, to May 4, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Graylog end of life mean for your organization?
When a version of Graylog reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Graylog should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Graylog reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Graylog versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Graylog has 25 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Graylog is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."