CVE-2026-125283: NGINX try_files vulnerability
Noroxi assessment
Priority: Monitor (action score 27/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: F5 NGINX Open Source 1.30.7, 1.31.9.
Low priority for now. Upgrade to F5 NGINX Open Source 1.30.7, 1.31.9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
When NGINX Plus or NGINX Open Source is configured to use the try_files and alias directives with a map variable, certain combinations of regular expression captures in map and try_files can cause a segmentation fault in an NGINX worker process. Impact: An attacker could leverage this vulnerability to cause an NGINX worker process to terminate unexpectedly. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
- Published
- Nov 18, 2026
- Updated
- Nov 19, 2026
- EPSS
- —
- CWE
- CWE-191
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · f5
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| f5 | dos | cpe:2.3:a:f5:dos |
| f5 | nginx gateway fabric | cpe:2.3:a:f5:nginx_gateway_fabric |
| f5 | nginx ingress controller | cpe:2.3:a:f5:nginx_ingress_controller |
| f5 | nginx instance manager | cpe:2.3:a:f5:nginx_instance_manager |
| f5 | nginx open source | cpe:2.3:a:f5:nginx_open_source |
| f5 | nginx plus | cpe:2.3:a:f5:nginx_plus |
| f5 | waf | cpe:2.3:a:f5:waf |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (f5). Independent of NVD's CPE analysis and usually ahead of it.
F5 NGINX Open Source
- 1.31.0 and later · before 1.31.9affected · semver
- 1.30.0 and later · before 1.30.7affected · semver
- 0.9.6 and lateraffected · semver
F5 NGINX Plus
- 37.1.0 and later · before 37.3.0.1affected
- 37.0.0 and later · before 37.0.8.1affected
- R33 and lateraffected
Affected versions · NVD (19)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- f5 dos4.5.0 and later · up to 4.7.0 inclusive
- f5 nginx gateway fabric1.5.0 and later · up to 1.6.2 inclusive
- f5 nginx gateway fabric2.0.0 and later · before 2.9.0
- f5 nginx ingress controller3.7.1 and later · up to 3.7.2 inclusive
- f5 nginx ingress controller4.0.0 and later · up to 4.0.1 inclusive
- f5 nginx ingress controller5.0.0 and later · up to 5.7.1 inclusive
- f5 nginx ingress controller2026
- f5 nginx instance manager2.19.0 and later · before 2.25.0
- f5 nginx open source0.9.6 and later · before 1.30.7
- f5 nginx open source1.31.0 and later · before 1.31.9
- f5 nginx plus37.0.0 and later · before 37.0.8.1
- f5 nginx plus37.1.0 and later · before 37.3.0.1
- f5 nginx plusr34
- f5 nginx plusr35
- f5 nginx plusr36
- f5 waf4.12.0 and later · up to 4.16.0 inclusive
- f5 waf5.4.0 and later · up to 5.8.0 inclusive
- f5 waf5.9.0 and later · before 5.14.4
- f5 waf5.15.0 and later · before 5.16.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | nginx | from 0 | — |
Same product
f5: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-42945NGINX ngx_http_rewrite_module vulnerability56Plan
- CVE-2026-42055NGINX ngx_http_proxy_v2_module and ngx_http_grpc_module vulnerability38Monitor
- CVE-2026-15176NGINX ngx_http_core_module vulnerability36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-48142Jun 17, 2026 · NGINX ngx_http_charset_module vulnerability25Monitor
- ← EarlierCVE-2026-118899Nov 18, 2026 · NGINX TLSv1.3 vulnerability34Monitor
- ← EarlierCVE-2026-123640Nov 18, 2026 · NGINX ngx_stream_ssl_preread_module vulnerability27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| F5 NGINX Open Source | 1.30.7 | Vendor (CNA) |
| F5 NGINX Open Source | 1.31.9 | Vendor (CNA) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-11-18 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-1 d
- Published
- Fix recordedsame day
- TodayNov 19, 2026+1 d
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1230070 days apartNGINX ngx_http_v2_module vulnerability36Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-191 · Integer Underflow (Wrap or Wraparound)CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturitynone → poc
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
- CVSS5.3 → 6.9
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.