This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied server name includes
Source GCVE Database
Not known to be exploited · CVSS 8.1 High : upgrade to 37.3.0.1 or 37.0.8.1 soon.
Data as of 18 Nov 2026, 20:23 UTC
Thin evidence
One scorer or none| CNA (f5) | CVSS 3.1 | 8.1 |
|---|---|---|
| CNA (f5) | CVSS 4.0 | 9.2 |
- Patch
- Available – fixed in 37.3.0.1, 37.0.8.1, 1.31.9 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade NGINX to 37.3.0.1 or 37.0.8.1 (Plus); 1.31.9 or 1.30.7 (Open Source).
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| F5NGINX Plus | Affected
| Fixed in
|
| F5NGINX Open Source | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, consider avoiding configurations that use variable server names with SSI or mirror directives that cause subrequests to the same server name.
Description
A use-after-free vulnerability exists in NGINX Plus and NGINX Open Source when configured as a proxy with variable server names and certain SSI or mirror directives. This flaw can be triggered by a specially crafted HTTP request, potentially causing worker process crashes, memory corruption, or remote code execution if ASLR is bypassed or disabled. The vulnerability has a high severity rating with a CVSS score of 8.1.