Nginx vulnerabilitiesAnd the versions its exploited flaws hit.
Nginx is made by F5. We track 41 published vulnerabilities listed under that exact name, across 556 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 10 October 2023. F5 lists newer releases under their own names, such as Nginx Controller, so check those pages too.
The most recent Nginx flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023. We keep watching the known-exploited list.
Is Nginx listed under other names? Yes.
F5 also lists Nginx under more specific names, such as Nginx Controller and Nginx Plus. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
- Nginx Controller18 published vulnerabilities
- Nginx Plus11 published vulnerabilities
- Nginx Open Source8 published vulnerabilities
- Nginx Ingress Controller7 published vulnerabilities
- Nginx Instance Manager6 published vulnerabilities
- Nginx API Connectivity Manager3 published vulnerabilities
- Nginx Agent2 published vulnerabilities
- Nginx Security Monitoring2 published vulnerabilities
- Nginx Openid Connect1 published vulnerability
- Nginx Controller API Management1 published vulnerability
- Nginx App Protect1 published vulnerability
- Nginx Service Mesh1 published vulnerability
Which versions of Nginx do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2023-44487Exploited list, 10 Oct 2023
HTTP/2 Rapid Reset Attack Vulnerability
1.9.5 to 1.25.2
Which Nginx vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 7.5HTTP/2 Rapid Reset Attack Vulnerability
HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).
Which Nginx flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
- 87%CVE-2013-2028High
The ngx_http_parse_chunked function in http/ngx_http_parse.c in nginx 1.3.9 through 1.4.0 allows remote attackers to cause a denial of service (crash) and execute arbitrary code via a chunked Transfer-Encoding...
- 82%CVE-2016-0742High
The resolver in nginx before 1.8.1 and 1.9.x before 1.9.10 allows remote attackers to cause a denial of service (invalid pointer dereference and worker process crash) via a crafted UDP DNS response.
- 82%CVE-2019-9513High
Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service.
- 75%CVE-2009-2629High
Buffer underflow in src/http/ngx_http_parse.c in nginx 0.1.0 through 0.5.37, 0.6.x before 0.6.39, 0.7.x before 0.7.62, and 0.8.x before 0.8.15 allows remote attackers to execute arbitrary code via crafted HTTP requests.
- 72%CVE-2010-2263Medium
nginx 0.8 before 0.8.40 and 0.7 before 0.7.66, when running on Windows, allows remote attackers to obtain source code or unparsed content of arbitrary files under the web document root by appending ::$DATA to the URI.
- 68%CVE-2013-4547High
nginx 0.8.41 through 1.4.3 and 1.5.x before 1.5.7 allows remote attackers to bypass intended restrictions via an unescaped space character in a URI.
- 63%CVE-2017-7529High
Nginx versions since 0.5.6 up to and including 1.13.2 are vulnerable to integer overflow vulnerability in nginx range filter module resulting into leak of potentially sensitive information triggered by specially...
- 60%CVE-2019-9511High
Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service.
Running Nginx? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).
- Matched to
- Nginx on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 41 published vulnerabilities listed under the name Nginx, across 556 versions. The most recent Nginx flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2023-44487.
F5 also lists Nginx under more specific names, such as Nginx Controller and Nginx Plus. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Each flaw names its own versions, usually as ranges. The newest, CVE-2023-44487, affects 1.9.5 to 1.25.2. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Nginx. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.