nginx End of Life: Supported Versions and Dates
Only two nginx branches are supported right now: mainline 1.31 (latest 1.31.8) and stable 1.30 (latest 1.30.6). Every older branch is out of support, including 1.28 and 1.29, which ended in April and May 2026.
6 mo left
nginx 1.31 gets security updates until 31 May 2027 (6 mo left). That is less than a year away. This date is our estimate: A mainline branch is replaced when the next mainline (1.33.0) opens, which has happened 3 to 8 weeks after each April stable release; we use 31 May 2027.
nginx.org has no long-term releases. A new stable branch comes out every April, made from the previous mainline, and the old stable branch stops getting fixes when it does. Odd-numbered branches are mainline. A mainline branch gets new features, bug fixes and security fixes until the next mainline branch opens, usually a few weeks after the April stable release.
nginx publishes no end dates in advance. For finished branches, the date we show is the day the replacing branch was released, taken from the official CHANGES files. For 1.30 and 1.31 the dates are estimates based on that April pattern.
If you installed nginx from your Linux distribution, the distribution may backport security fixes to an older version. That support comes from the distribution, not from nginx.org.
Nginx support dates
| Version | Released | Supported until | Time left | Status | Latest |
|---|---|---|---|---|---|
| nginx 1.31 | Estimated[1] | 6 mo left | Ending within a year | 1.31.8 | |
| nginx 1.30 | Estimated[1] | 4 mo left | Ending within a year | 1.30.6 | |
| Nginx 1.29 | Confirmed[2] | Ended | Unsupported | 1.29.8 | |
| Nginx 1.28 | Confirmed[3] | Ended | Unsupported | 1.28.3 | |
| Nginx 1.27 | Confirmed[2] | Ended | Unsupported | 1.27.5 | |
| Nginx 1.26 | Confirmed[4] | Ended | Unsupported | 1.26.3 | |
| Nginx 1.25 | Confirmed[2] | Ended | Unsupported | 1.25.5 | |
| Nginx 1.24 | Confirmed[5] | Ended | Unsupported | 1.24.0 | |
| Nginx 1.23 | Confirmed[2] | Ended | Unsupported | 1.23.4 | |
| Nginx 1.22 | Confirmed[6] | Ended | Unsupported | 1.22.1 | |
| Nginx 1.21 | Confirmed[2] | Ended | Unsupported | 1.21.6 | |
| Nginx 1.20 | Confirmed[7] | Ended | Unsupported | 1.20.2 | |
| Nginx 1.19 | Confirmed[2] | Ended | Unsupported | 1.19.10 | |
| Nginx 1.18 | Confirmed[8] | Ended | Unsupported | 1.18.0 | |
| Nginx 1.16 | Confirmed[9] | Ended | Unsupported | 1.16.1 | |
| Nginx 1.14 | Confirmed[10] | Ended | Unsupported | 1.14.2 | |
| Nginx 1.12 | Confirmed[11] | Ended | Unsupported | 1.12.2 | |
| Nginx 1.10 | Confirmed[12] | Ended | Unsupported | 1.10.3 | |
| Nginx 1.8 | Confirmed[13] | Ended | Unsupported | 1.8.1 | |
| Nginx 1.6 | Confirmed[14] | Ended | Unsupported | 1.6.3 | |
| Nginx 1.4 | Confirmed[15] | Ended | Unsupported | 1.4.7 | |
| Nginx 1.2 | Confirmed[16] | Ended | Unsupported | 1.2.9 | |
| Nginx 1.0 | Confirmed[17] | Ended | Unsupported | 1.0.15 |
Official published by the vendor · Confirmed observed (for example, patches stopped) · Estimated our forecast, with the rule stated · How we date things
Timeline
Active supportSupported untilExtended supportEstimatedEnded
What happens when support ends
Will it still run?
nginx keeps serving traffic. Nothing is disabled when a branch is superseded.
Will it get security fixes?
nginx.org publishes security fixes only for the current mainline and stable branches. When a CVE is announced, older branches get no patch from nginx.org.
What stops working?
New modules and features, such as recent HTTP/3 and ACME changes, land only in mainline and the next stable branch. Third-party dynamic modules built for a newer version will not load on an older binary, because nginx checks module compatibility at load time.
What are my options?
- Move to stable 1.30 or mainline 1.31 from the nginx.org packages for your distribution.
- If you use your distribution's nginx package, check that the distribution still patches it.
- Pick mainline if you can update often. nginx recommends it for most users, because it gets every fix first.
What to do
Check your version with nginx -v, or nginx -V to see the build options and modules too.
To upgrade, add the official nginx.org repository for your distribution (see nginx.org/en/linux_packages.html), install the package, then test the config with nginx -t and reload.
Nginx versions: end of support, one by one
nginx 1.31 end of life Ending within a year
nginx 1.31 gets security updates until 31 May 2027 (6 mo left). That is less than a year away. This date is our estimate: A mainline branch is replaced when the next mainline (1.33.0) opens, which has happened 3 to 8 weeks after each April stable release; we use 31 May 2027. Current mainline branch.
nginx 1.30 end of life Ending within a year
nginx 1.30 gets security updates until 15 Apr 2027 (4 mo left). That is less than a year away. This date is our estimate: nginx ends a stable branch when the next stable branch (1.32.0) is released, which has happened every April since 2012; we use mid-April 2027. Current stable branch.
Nginx 1.29 end of life Unsupported
Nginx 1.29 stopped getting security updates on 13 May 2026 and is no longer supported. Superseded by mainline 1.31.0 on 13 May 2026.
Nginx 1.28 end of life Unsupported
Nginx 1.28 stopped getting security updates on 14 Apr 2026 and is no longer supported. Superseded by stable 1.30.0 on 14 April 2026.
Nginx 1.27 end of life Unsupported
Nginx 1.27 stopped getting security updates on 24 Jun 2025 and is no longer supported.
Nginx 1.26 end of life Unsupported
Nginx 1.26 stopped getting security updates on 23 Apr 2025 and is no longer supported.
Nginx 1.25 end of life Unsupported
Nginx 1.25 stopped getting security updates on 29 May 2024 and is no longer supported.
Nginx 1.24 end of life Unsupported
Nginx 1.24 stopped getting security updates on 23 Apr 2024 and is no longer supported.
Nginx 1.23 end of life Unsupported
Nginx 1.23 stopped getting security updates on 23 May 2023 and is no longer supported.
Nginx 1.22 end of life Unsupported
Nginx 1.22 stopped getting security updates on 11 Apr 2023 and is no longer supported.
Nginx 1.21 end of life Unsupported
Nginx 1.21 stopped getting security updates on 21 Jun 2022 and is no longer supported.
Nginx 1.20 end of life Unsupported
Nginx 1.20 stopped getting security updates on 24 May 2022 and is no longer supported.
Nginx 1.19 end of life Unsupported
Nginx 1.19 stopped getting security updates on 25 May 2021 and is no longer supported.
Nginx 1.18 end of life Unsupported
Nginx 1.18 stopped getting security updates on 20 Apr 2021 and is no longer supported.
Nginx 1.16 end of life Unsupported
Nginx 1.16 stopped getting security updates on 21 Apr 2020 and is no longer supported.
Nginx 1.14 end of life Unsupported
Nginx 1.14 stopped getting security updates on 23 Apr 2019 and is no longer supported.
Nginx 1.12 end of life Unsupported
Nginx 1.12 stopped getting security updates on 17 Apr 2018 and is no longer supported.
Nginx 1.10 end of life Unsupported
Nginx 1.10 stopped getting security updates on 12 Apr 2017 and is no longer supported.
Nginx 1.8 end of life Unsupported
Nginx 1.8 stopped getting security updates on 26 Apr 2016 and is no longer supported.
Nginx 1.6 end of life Unsupported
Nginx 1.6 stopped getting security updates on 21 Apr 2015 and is no longer supported.
For businesses and auditors
Paste this into a risk register, an audit response or an insurance questionnaire. It updates with the version picked above.
As of 16 Nov 2026: nginx 1.31 gets security updates until 31 May 2027 (6 mo left). That is less than a year away. This date is our estimate: A mainline branch is replaced when the next mainline (1.33.0) opens, which has happened 3 to 8 weeks after each April stable release; we use 31 May 2027. Source: https://www.itechtics.com/eol/nginx/, verified 11 Nov 2026.Get Nginx end-of-life alerts
We email you 90, 30 and 7 days before a Nginx version loses support, and when a vendor moves a date. One email at most per day, unsubscribe in one click.
Prefer your calendar? Add Nginx end dates to your calendar (subscribe to the link in Outlook, Google or Apple Calendar).
F5 / nginx.org support policy
nginx.org maintains two branches at a time: mainline (odd minor numbers) with new features and fixes, and stable (even minor numbers) with critical fixes only. Each April a new stable branch is cut from mainline, and the previous stable branch is no longer maintained.
What changed
- nginx 1.31 was released.
- Nginx 1.29 reached end of support.
- nginx 1.30 was released.
- Nginx 1.28 reached end of support.
Frequently asked questions
Which Nginx versions are still supported?
As of 16 Nov 2026, these Nginx versions get security updates: nginx 1.31, nginx 1.30.
When does nginx 1.31 support end?
nginx 1.31 gets security updates until 31 May 2027 (6 mo left). That is less than a year away. This date is our estimate: A mainline branch is replaced when the next mainline (1.33.0) opens, which has happened 3 to 8 weeks after each April stable release; we use 31 May 2027.
What happens when Nginx reaches end of life?
nginx keeps serving traffic. Nothing is disabled when a branch is superseded. nginx.org publishes security fixes only for the current mainline and stable branches. When a CVE is announced, older branches get no patch from nginx.org.
Which nginx versions are supported?
Mainline 1.31 and stable 1.30. As of November 2026 the latest releases are 1.31.8 and 1.30.6.
Is nginx 1.28 still supported?
No. 1.28 was the stable branch until 1.30.0 came out on 14 April 2026. Its last release was 1.28.3, in March 2026.
Is nginx 1.24 still supported?
Not by nginx.org. Support ended when 1.26.0 came out in April 2024. Ubuntu 24.04 ships 1.24 and backports security fixes to its own package.
Should I use nginx mainline or stable?
nginx recommends mainline for most users, because it gets all bug fixes first. Stable changes less often and gets only critical fixes.
Does nginx have LTS releases?
No. Each stable branch is maintained for about a year, until the next stable branch comes out.
Sources and method
- nginx.org/en/download.html
- nginx.org/en/CHANGES
- nginx.org/en/CHANGES-1.28
- nginx.org/en/CHANGES-1.26
- nginx.org/en/CHANGES-1.24
- nginx.org/en/CHANGES-1.22
- nginx.org/en/CHANGES-1.20
- nginx.org/en/CHANGES-1.18
- nginx.org/en/CHANGES-1.16
- nginx.org/en/CHANGES-1.14
- nginx.org/en/CHANGES-1.12
- nginx.org/en/CHANGES-1.10
- nginx.org/en/CHANGES-1.8
- nginx.org/en/CHANGES-1.6
- nginx.org/en/CHANGES-1.4
- nginx.org/en/CHANGES-1.2
- nginx.org/en/CHANGES-1.0
- nginx download page
- nginx mainline CHANGES
- nginx 1.30 CHANGES
- nginx news
Dates come from the vendor's own lifecycle pages wherever they exist and are checked against them on a schedule. A date is Official when the vendor publishes it, Confirmed when we have seen the updates stop, and Estimated when the vendor publishes nothing and we forecast it from their past behaviour. The rule is shown next to every estimate. Status and time left are worked out from today's date.
Spotted a wrong date? Tell us and include the source.