Kong Gateway 3.13 · Version Status
Kong Gateway 3.13 End of Life Date
Kong Gateway 3.13 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.
⚡
Kong Gateway 3.13 reaches end of life on December 18, 2026. Plan your migration now — 61 days remaining.
📅 Get reminded before Kong Gateway 3.13 reaches EOL on December 18, 2026 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Dec 18, 2026
61 days remaining
Latest Release
—
Standard release
Release Date
Dec 18, 2025
Kong Gateway 3.13 series
Where these dates come from
End of lifeDec 18, 2026Vendor's own page (our correction) · developer.konghq.com · checked Oct 18, 2026medium · 1 source agrees ReleaseDec 18, 2025Vendor's own page (our correction) · developer.konghq.com · checked Oct 18, 2026medium · 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
Kong Gateway 3.13 was released on December 18, 2025 and support is scheduled to end on December 18, 2026 — a planned supported lifespan of 1 year, in line with the 1 year median for Kong Gateway releases. It is not an LTS release; Kong Gateway reserves longer patch windows for its LTS versions.
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 →
Extended Support
Extended Kong Gateway 3.13 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All Kong Gateway Versions
| Version | Latest | EOL Date | Status |
|---|
| 2.8 LTS |
2.8.5 |
Jun 24, 2024 |
EOL |
| 3.0 |
3.0.2 |
Dec 9, 2022 |
EOL |
| 3.1 |
3.1.1 |
Feb 21, 2023 |
EOL |
| 3.2 |
3.2.2 |
May 18, 2023 |
EOL |
| 3.3 |
3.3.1 |
Aug 9, 2023 |
EOL |
| 3.4 LTS |
3.4.2 |
Aug 31, 2026 |
EOL |
| 3.5 |
3.5.0 |
Feb 15, 2024 |
EOL |
| 3.6 |
3.6.1 |
May 28, 2024 |
EOL |
What does Kong Gateway 3.13 end of life mean?
When Kong Gateway 3.13 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 Kong Gateway 3.13 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Kong Gateway 3.16 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Kong Gateway 3.13 reach end of life?
Kong Gateway 3.13 reaches end of life on December 18, 2026. That is 61 days remaining.
Is Kong Gateway 3.13 still supported?
Kong Gateway 3.13 is still supported but approaching end of life on December 18, 2026. Begin planning your migration now.
What should I upgrade to from Kong Gateway 3.13?
The recommended upgrade from Kong Gateway 3.13 is
Kong Gateway 3.16 — the latest actively supported version. Check the
Kong Gateway full timeline for all supported versions.
What are the security risks of running Kong Gateway 3.13 past EOL?
When Kong Gateway 3.13 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 Kong Gateway should migrate immediately or implement compensating controls.