NGINX Open-Source ngx_http_v3_module vulnerability
NGINX Open Source has a vulnerability in the ngx_http_v3_module module. When NGINX Open Source is configured to use the HTTP/3 QUIC module, a remote unauthenticated attacker along with conditions beyond their control can use a specially crafted HTTP/3 session to reopen a QPACK encoder stream. This may cause a Use-after-Free 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. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
- Published
- Jun 17, 2026
- Updated
- Jul 16, 2026
- EPSS
- 1.1% · 65th percentile
- CWE
- CWE-416
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
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.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- f5 nginx open source1.31.0 and later · before 1.31.2
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.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | nginx | all versions | — |
| openSUSE:Tumbleweed | nginx | before 1.31.2-1.1 | 1.31.2-1.1 |
| Red Hat:hummingbird:1 | nginx | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
| Red Hat:hummingbird:1 | nginx-all-modules | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
Same product
f5: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-42533NGINX Map directive and Regex matching vulnerability36Monitor
- CVE-2026-60005NGINX ngx_http_slice_module vulnerability35Monitor
- CVE-2026-66362Description:
When NGINX Plus is configured as the data plane for NGINX Gateway Fabric, an injection vulnerability exists in the NGINX config34Monitor
- CVE-2026-50107NGINX Gateway Fabric vulnerability34Monitor
- CVE-2026-11311NGINX Gateway Fabric vulnerability34Monitor
- CVE-2026-56434NGINX ngx_http_ssi_module vulnerability33Monitor
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 |
|---|---|---|
| opensuse:nginx | 1.31.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:nginx | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nginx-all-modules | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
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 ×3
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-06-19 |
| Proof-of-concept repository on GitHub | stars:5 | 2026-06-19 |
| Proof-of-concept repository on GitHub | stars:3 | 2026-06-19 |
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.
- Published
- First PoC+2 d
- TodaySep 30, 2026+105 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- "F5 acknowledges Trung Nguyen (@everping)CyStack, Zhenpeng (Leo) Lin (depthfirst), Evan Hellman (@xintenseapple)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-5643428 days apartNGINX ngx_http_ssi_module vulnerability33Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- my.f5.com/manage/s/article/K000161616
- access.redhat.com/errata/RHSA-2026:20351
- access.redhat.com/security/cve/CVE-2026-42530
- bugzilla.redhat.com/show_bug.cgi?id=2489872
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42530.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.