CVE-2026-15176 — NGINX ngx_http_core_module vulnerability
A vulnerability exists in NGINX Plus and NGINX Open Source when a location is configured that uses the alias directive together with rewrite and a set or return directive referencing the $request_filename variable. Alternatively, the same result could be achieved when the $request_filename variable is used in an access log format directive. An unauthenticated attacker along with conditions beyond their 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. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution. 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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (F5 Nginx Open Source, F5 Nginx Plus).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| F5 | Nginx Open Source | ≥ 1.31.0 and < 1.31.7≥ 0.1.29 and < 1.30.6 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| F5 | Nginx Plus | ≥ 37.1.0 and < 37.1.0.1≥ 37.0.0 and < 37.0.5.1≥ R36≥ R35≥ R34≥ R33 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.2 | CVSS 4.0 | Critical | — | — | f5sirt@f5.com via NIST National Vulnerability Database |
| 9.2 | CVSS 4.0 | Critical | — | — | f5 via CVE Program (cve.org) e CISA ADP |
| 8.1 | CVSS 3.1 | High | 2.2 | 5.9 | f5sirt@f5.com via NIST National Vulnerability Database |
| 8.1 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.1 | CVSS 3.1 | High | — | — | f5 via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: f5sirt@f5.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Source status changed · Received → Awaiting Analysis
- Affected products added · f5/nginx plus, f5/nginx open source
- Record published
- CVSS changed · 8.1
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
3 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-97205 NGINX ngx_http_core_module vulnerability 1d
- Medium CVE-2026-97629 NGINX ngx_http_ssl_module vulnerability 1d
- Medium CVE-2026-95101 NGINX ngx_http_v3_module vulnerability 1d
- High CVE-2026-93479 NGINX map directive and regex matching vulnerability 1d
- High CVE-2026-60005 NGINX ngx_http_slice_module vulnerability Jul 15, 2026
- Medium CVE-2026-60065 NGINX Plus ngx_stream_mqtt_filter_module vulnerability Jul 15, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-15176 is "NGINX ngx_http_core_module vulnerability", rated High. It affects Nginx Open Source (F5); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.1 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.