CVE-2026-123634: NGINX resolver vulnerability
Noroxi assessment
Priority: Monitor (action score 36/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. Special conditions such as timing or configuration are required.
- Fixed version: F5 NGINX Open Source 1.30.7, 1.31.9.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
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
This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied server name includes variables, and a Server Side Includes (SSI) or mirror directive sends a subrequest to a location that resolves the same server name. Under these conditions, a specially crafted HTTP request may cause a use-after-free condition in a worker process. An attacker may also be able to execute code if Address Space Layout Randomization (ASLR) is disabled or the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or perform remote code execution (RCE) 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-416
Report tools
Action score
36
Low priority for now.
- CVSS
- 36 / 40 · 9.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · f5
- 8.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 nginx on your server exposed to the internet?Run a port scan
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.
—
Using nginx plus? Add it to your stack and be the first to know about CVEs like this one. (Nginx)
Is nginx on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanVersions 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.6.18 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
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-27654NGINX ngx_http_dav_module vulnerability43Plan
- CVE-2026-123007NGINX ngx_http_v2_module vulnerability36Monitor
- CVE-2026-121810NGINX ngx_http_v3_module vulnerability36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-113425Nov 18, 2026 · NGINX ngx_mail_proxy_module vulnerability36Monitor
- ← EarlierCVE-2026-120967Nov 18, 2026 · NGINX ngx_stream_ssl_module vulnerability25Monitor
- ← EarlierCVE-2026-120993Nov 18, 2026 · NGINX ngx_stream_ssl_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.
- F5 acknowledges Xint.io for bringing this issue to our attention and following the highest standardscoordinated disclosure.reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1134250 days apartNGINX ngx_mail_proxy_module vulnerability36Monitor
- CVE-2026-1218100 days apartNGINX ngx_http_v3_module vulnerability36Monitor
- CVE-2026-9720535 days apartNGINX ngx_http_core_module vulnerability36Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1566 · Nov 18, 2026(NGINX Yazılımında Tespit Edilen Kritik Güvenlik Zafiyetleri (NGINX2Root))
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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✗ → ✓
- CVSS8.1 → 9.2
- Severityhigh → critical
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.