nginx
Server Appnginx 1.31 is the newest actively maintained release, currently at patch 1.31.5. 2 of 23 tracked cycles remain supported.
Support pattern
How nginx has behaved across the cycles tracked here, rather than what its policy documents state. Useful for judging how much runway a version is likely to have before you commit to it.
Support windows have stayed consistent across the tracked history, so past cycles are a reasonable guide to what a new one will get.
Computed from release and end-of-life dates tracked for nginx. Medians are used rather than averages so one unusually short or long release does not skew the figure. Cycles with no recorded end-of-life date are excluded from the support window.
How nginx versioning, EOL & security support work
nginx does not run a single sequential release line; it maintains two parallel branches at once. Mainline is where new features and all bug fixes land first, identified by an odd second version digit. Stable is forked periodically from mainline and carries forward only the fixes accumulated up to that fork point, identified by an even second version digit. Mainline gets new releases every few weeks; stable is updated far less often, only when a fix, especially a security fix, needs to be backported.
nginx discloses vulnerabilities through its official security advisories page, with the reporting process documented in its GitHub repository. Each advisory states exactly which mainline and stable version ranges are vulnerable and which are fixed, and that fixed-version list only ever covers branches still receiving updates. Running an older version than the current fixed line means an already-public, already-patched vulnerability can be sitting unaddressed in that install.
Sources: nginx: NGINX Versioning Explained, nginx Security Advisories
Release lifecycle
Get an email when nginx ships a release, announces an end-of-life date, or moves a date it already announced.
Get nginx alerts