CVE Tools
Track your stack

CVE-2026-42945

NGINX ngx_http_rewrite_module vulnerability

No known exploitation. EPSS puts it in the 89th percentile. Fixed versions are out.

CVSS 3.18.1HighEPSS percentile89th3.4% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix5 products5 fixed builds listed below

Published Updated Sources: CVE.org, NVD, BDU, CSAF

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • F5 NGINX PlusAffected: ≥ R36, < R36 P4Upgrade to: R36 P4Affected: ≥ R32, < R32 P6Upgrade to: R32 P6Fixed buildsR37Stated by: CVE record
  • F5 NGINX Open SourceAffected: ≥ 0.6.27, < 1.30.1Upgrade to: 1.30.1Fixed builds1.31.0Stated by: CVE record
  • F5 DosAffected: ≥ 4.3.0, ≤ 4.7.0Upgrade to: after 4.7.0Stated by: NVD
  • F5 Nginx Gateway FabricAffected: ≥ 1.3.0, ≤ 1.6.2Upgrade to: after 1.6.2Stated by: NVD
  • F5 Nginx Ingress ControllerAffected: ≥ 3.5.0, ≤ 3.7.2Upgrade to: after 3.7.2Stated by: NVD

Versions as the sources state them. 14 more products have version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

Coverage timeline

2 publishers

  1. Vendor patch released

    ·The Hacker News summary

  2. Technical analysis published

    ·The Hacker News summary

Sourced from public security reporting — each date is when it was published, not when it happened. 4 further articles named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_rewrite_module module. This vulnerability exists when the rewrite directive is followed by a rewrite, if, or set directive and an unnamed Perl-Compatible Regular Expression (PCRE) capture (for example, $1, $2) with a replacement string that includes a question mark (?). An unauthenticated attacker along with conditions beyond its control can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow in the NGINX worker process leading to a restart. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS89th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

3.4% chance of exploitation activity in the next 30 days, which ranks it in the 89th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

37 events over 145 days, from the signal feeds we watch.

  1. EPSS band changehigh → low
  2. EPSS band changehigh → low
  3. EPSS band changehigh → lowepss band change
  4. Patch availableworkaround available, record updated
  5. Patch availableworkaround available, record updated
  6. Patch availableworkaround available, record updated

Affected products

And 4 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 8.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 53 more references. See all after sign-in

In the news

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for NGINX Open Source, not every advisory.