Graylog 7.2 · Version Status
Graylog 7.2 End of Life Date
Graylog 7.2 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
Graylog 7.2 is actively supported. EOL date: October 13, 2027.
📅 Get reminded before Graylog 7.2 reaches EOL on October 13, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Oct 13, 2027
348 days remaining
Latest Release
7.2.1
Standard release
Release Date
Oct 13, 2026
Graylog 7.2 series
Where these dates come from
End of lifeOct 13, 2027endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseOct 13, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Graylog 7.2 was released on October 13, 2026 and support is scheduled to end on October 13, 2027 — a planned supported lifespan of 1 year, in line with the 1 year median for Graylog releases. Its most recent patch is 7.2.1, published October 19, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
| 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 7.2 end of life mean?
When Graylog 7.2 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Graylog 7.2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Graylog 7.2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Graylog 7.2 reach end of life?
Graylog 7.2 reaches end of life on October 13, 2027. That is 348 days remaining.
Is Graylog 7.2 still supported?
Yes, Graylog 7.2 is currently supported. The EOL date is October 13, 2027.
What should I upgrade to from Graylog 7.2?
The recommended upgrade from Graylog 7.2 is
Graylog 7.2 — the latest actively supported version. Check the
Graylog full timeline for all supported versions.
What are the security risks of running Graylog 7.2 past EOL?
When Graylog 7.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Graylog should migrate immediately or implement compensating controls.