Ingress NGINX 1 End of Life Date
Ingress NGINX 1 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.
Ingress NGINX 1 was released on August 24, 2021 and support ended on March 31, 2026 — a supported lifespan of 4 years and 7 months. The last patch it will ever receive is 1.15.1, published March 19, 2026 — 12 days before support ended. It has been without security patches for 6 months.
Commercial vendors offer security patches beyond EOL. Right now that coverage spans Ingress NGINX 1.15.1, with 60+ post-EOL CVE fixes documented in vendor release notes. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| → 1 | 1.15.1 | Mar 31, 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.