Kong Gateway · Lifecycle Status

Kong Gateway End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Kong Gateway versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Kong Gateway 3.4.2 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
3.4.2
3.4 series
Next EOL
None upcoming
Active Versions
2
of 11 total
EOL Versions
9
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 202220232024202520262.83.03.13.23.33.43.53.63.73.83.9TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
2.8 LTS 2.8.5 Mar 1, 2022 Jun 24, 2024 684 days past EOL EOL
3.0 3.0.2 Sep 12, 2022 Dec 9, 2022 1247 days past EOL EOL
3.1 3.1.1 Dec 6, 2022 Feb 21, 2023 1173 days past EOL EOL
3.2 3.2.2 Feb 20, 2023 May 18, 2023 1087 days past EOL EOL
3.3 3.3.1 May 18, 2023 Aug 9, 2023 1004 days past EOL EOL
3.4 LTS 3.4.2 Aug 9, 2023 Already EOL Supported Active
3.5 3.5.0 Nov 8, 2023 Feb 15, 2024 814 days past EOL EOL
3.6 3.6.1 Feb 9, 2024 May 28, 2024 711 days past EOL EOL
3.7 3.7.1 May 28, 2024 Sep 9, 2024 607 days past EOL EOL
3.8 3.8.1 Sep 9, 2024 Dec 12, 2024 513 days past EOL EOL
3.9 3.9.1 Dec 12, 2024 Already EOL Supported Active

What does Kong Gateway end of life mean for your organization?

When a Kong Gateway version 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: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Kong Gateway 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Kong Gateway?
See the full table above for all Kong Gateway version EOL dates.
What is the latest supported version of Kong Gateway?
The latest active version of Kong Gateway is 3.4.2. Always verify against the table above as support windows can change.
What happens when Kong Gateway reaches end of life?
When Kong Gateway reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Kong Gateway?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Kong Gateway versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →