Ingress NGINX 1 End of Life Date
Ingress NGINX 1 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (kubernetes.io); the source of each date is on the product page.
Ingress NGINX 1 was released on August 24, 2021 and support ended in March 2026 — a supported lifespan of 4 years and 7 months. Its latest release on record is 1.15.1, published March 19, 2026 — in the month support ended. It has been past its end-of-life date for 8 months.
Extended support for Ingress NGINX exists: vetted vendors ship security patches past the official date. Right now that coverage spans Ingress NGINX 1.15.1, with 60+ post-EOL CVE fixes documented in vendor release notes. Whether it covers Ingress NGINX 1 is part of what we check. Leave an email and we reply within one business day with matched options and pricing guidance, or an honest "no vendor covers this version." Free, no obligation; vendors do not pay for placement.
| Version | Latest | EOL Date | Status |
|---|---|---|---|
| → 1 | 1.15.1 | Mar 2026 | EOL |
What does Ingress NGINX 1 end of life mean?
When Ingress NGINX 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: 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 Ingress NGINX 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.