CVE-2026-1642 — NGINX vulnerability
A vulnerability exists in NGINX OSS and NGINX Plus when configured to proxy to upstream Transport Layer Security (TLS) servers. An attacker with a man-in-the-middle (MITM) position on the upstream server side—along with conditions beyond the attacker's control—may be able to inject plain text data into the response from an upstream proxied server. 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
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (medium)+3
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 Gateway Fabric, F5 Nginx Ingress Controller, F5 Nginx Instance Manager…).
- 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 (integrity), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| F5 | Nginx Gateway Fabric | ≥ 2.0.0 and < 2.4.1≥ 1.2.0 and ≤ 1.6.2 | Vulnerable | NIST National Vulnerability Database |
| F5 | Nginx Ingress Controller | ≥ 4.0.0 and ≤ 4.0.1≥ 5.0.0 and < 5.3.3≥ 3.4.0 and ≤ 3.7.2 | Vulnerable | NIST National Vulnerability Database |
| F5 | Nginx Instance Manager | ≥ 2.15.1 and ≤ 2.21.0 | Vulnerable | NIST National Vulnerability Database |
| F5 | Nginx Open Source | ≥ 1.3.0 and < 1.29.5 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| F5 | Nginx Open Source | ≥ 1.29.0 and < 1.29.5≥ 1.3.0 and < 1.28.2 | Vulnerable | NIST National Vulnerability Database |
| F5 | Nginx Plus | ≥ R36 and < R36 P2≥ R32 and < R32 P4≥ R33≥ R34≥ R35 and < R35 P1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| F5 | Nginx Plus |
≥ r33 and < r35version r32version r32-p1version r32-p2version r36-p1version r36version r35version r34-p2 and 5 moreversion r34-p1version r33-p3version r33-p2version r33-p1version r32-p3 |
Vulnerable | NIST National Vulnerability Database |
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 |
|---|---|---|---|---|---|
| 8.2 | CVSS 4.0 | High | — | — | f5sirt@f5.com via NIST National Vulnerability Database |
| 8.2 | CVSS 4.0 | High | — | — | f5 via CVE Program (cve.org) e CISA ADP |
| 5.9 | CVSS 3.1 | Medium | 2.2 | 3.6 | f5sirt@f5.com via NIST National Vulnerability Database |
| 5.9 | CVSS 3.1 | Medium | — | — | f5 via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N (score shown at the top: f5sirt@f5.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.39%
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).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · f5/nginx open source, f5/nginx plus
- SSVC assessment updated
- Record published
- CVSS changed · 5.9
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-96615 NGINX Gateway Fabric vulnerability 1d
- 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-94197 NGINX Ingress Controller vulnerability 1d
- High CVE-2026-93479 NGINX map directive and regex matching vulnerability 1d
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 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-1642 is "NGINX vulnerability", rated Medium. It affects Nginx Gateway Fabric (F5); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.9 describes technical severity. EPSS 0.39% estimates the probability of exploitation in 30 days; neither replaces your asset context. 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.