CISA list

nginx versions

nginx: update to 1.31.9 or 1.30.7. 1.29 and older have reached end of life in the lifecycle data.

Data: .

Which nginx branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are counted at the end of the page.

Which nginx branch to run
BranchStatusNewest safe releaseUpgrade to
1.319 CVE records that this page readsFixes, no end date announced1.31.91.31.9 (this branch)
1.3013 CVE records that this page readsFixes, no end date announced1.30.71.30.7 (this branch)
1.297 CVE records that this page readsEnded on 13 May 2026None, the branch has ended1.30.7 (move to 1.30)
1.286 CVE records that this page readsEnded on 14 April 2026None, the branch has ended1.30.7 (move to 1.30)
1.27Ended on 24 June 2025None, the branch has ended1.30.7 (move to 1.30)
1.264 CVE records that this page readsEnded on 23 April 2025None, the branch has ended1.30.7 (move to 1.30)
1.252 CVE records that this page readsEnded on 29 May 2024None, the branch has ended1.30.7 (move to 1.30)
1.24Ended on 23 April 2024None, the branch has ended1.30.7 (move to 1.30)
1.23Ended on 23 May 2023None, the branch has ended1.30.7 (move to 1.30)
1.22Ended on 11 April 2023None, the branch has ended1.30.7 (move to 1.30)
1.21Ended on 21 June 2022None, the branch has ended1.30.7 (move to 1.30)
1.20Ended on 24 May 2022None, the branch has ended1.30.7 (move to 1.30)
1.19Ended on 25 May 2021None, the branch has ended1.30.7 (move to 1.30)
1.18Ended on 20 April 2021None, the branch has ended1.30.7 (move to 1.30)
1.17Ended on 26 May 2020None, the branch has ended1.30.7 (move to 1.30)
1.16Ended on 20 April 2020None, the branch has ended1.30.7 (move to 1.30)
1.15Ended on 21 May 2019None, the branch has ended1.30.7 (move to 1.30)
1.14Ended on 23 April 2019None, the branch has ended1.30.7 (move to 1.30)
1.13Ended on 5 June 2018None, the branch has ended1.30.7 (move to 1.30)
1.12Ended on 17 April 2018None, the branch has ended1.30.7 (move to 1.30)
1.11Ended on 25 April 2017None, the branch has ended1.30.7 (move to 1.30)
1.10Ended on 12 April 2017None, the branch has ended1.30.7 (move to 1.30)
1.9Ended on 24 May 2016None, the branch has ended1.30.7 (move to 1.30)
1.8Ended on 26 April 2016None, the branch has ended1.30.7 (move to 1.30)
1.7Ended on 28 April 2015None, the branch has ended1.30.7 (move to 1.30)
1.6Ended on 21 April 2015None, the branch has ended1.30.7 (move to 1.30)
1.5Ended on 24 April 2014None, the branch has ended1.30.7 (move to 1.30)
1.4Ended on 24 April 2014None, the branch has ended1.30.7 (move to 1.30)
1.3Ended on 7 May 2013None, the branch has ended1.30.7 (move to 1.30)
1.2Ended on 24 April 2013None, the branch has ended1.30.7 (move to 1.30)
1.1Ended on 15 May 2012None, the branch has ended1.30.7 (move to 1.30)
1.0Ended on 23 April 2012None, the branch has ended1.30.7 (move to 1.30)

Exploited, or likely to be

CVE records for nginx that CISA lists as exploited, that have a public exploit, or that EPSS rates 0.50 or more, with the release that fixes each in every branch.

Exploited, or likely to be
RecordSigns of exploitationFixed in
CVE-2026-42945NGINX ngx_http_rewrite_module vulnerability9.2 Critical · published 13 May 2026EPSS 0.50 or moreFixed in 1.30.1

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

This page reads 47 CVE records that F5's CVE Numbering Authority published and that name nginx. The fixes are from the 28 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

No release of a branch that has ended is called safe here.

Some records give a range that starts in an older branch and ends in a newer one. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the older branches it runs across. Only a range that runs across branches that have all ended is placed: a range that reaches a branch that still gets fixes would name that branch's newest release as affected, which a project that also fixes its older branches does not mean. Such a record is counted at the end of the page.

19 records are not placed on a branch, so no branch or release row counts them: CVE-2022-41741, CVE-2022-41742, CVE-2024-7347, CVE-2025-23419, CVE-2026-1642, CVE-2026-9256, CVE-2026-42055, CVE-2026-48142, CVE-2026-90439 and CVE-2026-95101 and 9 others.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)