When NGINX Plus or NGINX Open Source is configured to use the try_files and alias directives with a map variable
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 37.3.0.1 or 37.0.8.1 when convenient.
Data as of 18 Nov 2026, 20:20 UTC
Thin evidence
One scorer or none| CNA (f5) | CVSS 3.1 | 5.3 |
|---|---|---|
| CNA (f5) | CVSS 4.0 | 6.9 |
- Patch
- Available – fixed in 37.3.0.1, 37.0.8.1, 1.31.9 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation 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, avoid configurations that combine try_files and alias directives with map variables using complex regular expression captures.
Description
A vulnerability in NGINX Plus and NGINX Open Source occurs when configured with try_files and alias directives using a map variable, where certain regular expression captures can cause a segmentation fault in a worker process. This leads to unexpected termination of the worker process, affecting availability. There is no impact on confidentiality or integrity, and no control plane exposure. The vulnerability has a medium severity score of 5.3.