NGINX 1.11 · Version Status
NGINX 1.11 End of Life Date
NGINX 1.11 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.
⚠
NGINX 1.11 is past end of life. This version no longer receives security patches. 3483 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 25, 2017
3483 days past EOL
Latest Release
1.11.13
Standard release
Release Date
May 24, 2016
NGINX 1.11 series
Where these dates come from
End of lifeApr 25, 2017Vendor's own page, read by our adapter · nginx.org · checked Nov 2, 2026high · 2 sources agree ReleaseMay 24, 2016Vendor's own page, read by our adapter · nginx.org · checked Nov 2, 2026high · 2 sources agree 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
NGINX 1.11 was released on May 24, 2016 and support ended on April 25, 2017 — a supported lifespan of 11 months, in line with the 1 year median for NGINX releases. Its latest release on record is 1.11.13, published April 4, 2017 — 21 days before support ended. It has been past its end-of-life date for 9 years and 7 months. 18 newer NGINX releases have shipped since.
Attack Surface
20/30 High 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.15 |
Apr 23, 2012 |
EOL |
| 1.1 |
1.1.19 |
May 15, 2012 |
EOL |
| 1.2 |
1.2.9 |
Apr 24, 2013 |
EOL |
| 1.3 |
1.3.16 |
May 7, 2013 |
EOL |
| 1.4 |
1.4.7 |
Apr 24, 2014 |
EOL |
| 1.5 |
1.5.13 |
Apr 24, 2014 |
EOL |
| 1.6 |
1.6.3 |
Apr 21, 2015 |
EOL |
| 1.7 |
1.7.12 |
Apr 28, 2015 |
EOL |
What does NGINX 1.11 end of life mean?
When NGINX 1.11 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 NGINX 1.11 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to NGINX 1.31 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does NGINX 1.11 reach end of life?
NGINX 1.11 reached end of life on April 25, 2017. This version is no longer receiving security patches.
Is NGINX 1.11 still supported?
No. NGINX 1.11 reached end of life on April 25, 2017 and is no longer receiving security patches.
What should I upgrade to from NGINX 1.11?
The recommended upgrade from NGINX 1.11 is
NGINX 1.31 — the latest actively supported version. Check the
NGINX full timeline for all supported versions.
What are the security risks of running NGINX 1.11 past EOL?
Since NGINX 1.11 reached end of life, the maintainers no longer issue 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 NGINX should migrate immediately or implement compensating controls.