CVE-2026-40460: NGINX ngx_quic_module vulnerability
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
- 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.1; azl3 nginx 1.28.3-1 on Azure Linux 3.0 1.28.3-2.
Low priority for now. Upgrade to F5 NGINX Open Source 1.30.1; azl3 nginx 1.28.3-1 on Azure Linux 3.0 1.28.3-2 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
Primary sources: NVD · CVE.org · FIRST EPSS
When NGINX Plus or NGINX Open Source are configured to use the HTTP/3 QUIC module, an attacker may be able to spoof their source IP address allowing for bypass of authorization or bypass of rate limiting. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
- Published
- May 13, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-290
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · f5
- 6.5
- 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:L/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
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- f5 dos4.3.0 and later · up to 4.7.0 inclusive
- f5 dos4.8.0
- f5 nginx gateway fabric1.3.0 and later · up to 1.6.2 inclusive
- f5 nginx gateway fabric2.0.0 and later · up to 2.6.0 inclusive
- f5 nginx ingress controller3.5.0 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.4.2 inclusive
- f5 nginx instance manager2.16.0 and later · up to 2.22.0 inclusive
- f5 nginx open source1.25.0 and later · up to 1.30.0 inclusive
- f5 nginx plusr32 and later · up to r36 inclusive
- f5 waf4.9.0 and later · up to 4.16.0 inclusive
- f5 waf5.1.0 and later · up to 5.8.0 inclusive
- f5 waf5.9.0 and later · up to 5.12.1 inclusive
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 laternot affected · semver
- 1.26.0 and later · before 1.30.1affected · semver
F5 NGINX Plus
- R37 and laternot affected
- R36 and later · before R36 P4affected
- R32 and later · before R32 P6affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | nginx | before 1.26.3-r1 | 1.26.3-r1 |
| Alpine:v3.22 | nginx | before 1.28.3-r1 | 1.28.3-r1 |
| Alpine:v3.24 | nginx | before 1.30.1-r0 | 1.30.1-r0 |
| Debian:13 | nginx | before 1.26.3-3+deb13u5 | 1.26.3-3+deb13u5 |
| Debian:14 | nginx | before 1.30.0-4 | 1.30.0-4 |
| openSUSE:Leap 16.0 | nginx | before 1.27.2-160000.6.1 | 1.27.2-160000.6.1 |
| openSUSE:Tumbleweed | nginx | before 1.31.0-1.1 | 1.31.0-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 |
| Red Hat:hummingbird:1 | nginx-core | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
| Red Hat:hummingbird:1 | nginx-filesystem | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
| Red Hat:hummingbird:1 | nginx-mod-devel | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
| Red Hat:hummingbird:1 | nginx-mod-http-geoip | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
| Red Hat:hummingbird:1 | nginx-mod-http-image-filter | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
| Red Hat:hummingbird:1 | nginx-mod-http-perl | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
| Red Hat:hummingbird:1 | nginx-mod-http-xslt-filter | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
| Red Hat:hummingbird:1 | nginx-mod-mail | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
| Red Hat:hummingbird:1 | nginx-mod-stream | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
| Red Hat:hummingbird:1 | nginx-mod-stream-geoip | before 0:1.30.2-1.hum1 | 0:1.30.2-1.hum1 |
| SUSE:Linux Enterprise Server 16.0 | nginx | before 1.27.2-160000.6.1 | 1.27.2-160000.6.1 |
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-42946NGINX ngx_http_scgi_module and ngx_http_uwsgi_module vulnerability33Monitor
Published before and after this one in the same product
- Later →CVE-2026-40701May 13, 2026 · NGINX ngx_http_ssl_module vulnerability25Monitor
- Later →CVE-2026-42934May 13, 2026 · NGINX ngx_http_charset_module vulnerability25Monitor
- Later →CVE-2026-48142Jun 17, 2026 · NGINX ngx_http_charset_module vulnerability25Monitor
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.1 | Vendor (CNA) |
| azl3 nginx 1.28.3-1 on Azure Linux 3.0 | 1.28.3-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| alpine:nginx | 1.26.3-r1 · Alpine:v3.21 | Package registry (OSV) |
| debian:nginx | 1.26.3-3+deb13u5 · Debian:13 | Package registry (OSV) |
| opensuse:nginx | 1.31.0-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) |
| red hat:nginx-core | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nginx-filesystem | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nginx-mod-devel | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nginx-mod-http-geoip | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nginx-mod-http-image-filter | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nginx-mod-http-perl | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nginx-mod-http-xslt-filter | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nginx-mod-mail | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nginx-mod-stream | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nginx-mod-stream-geoip | 0:1.30.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:nginx | 1.27.2-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
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.
- 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-290 · Authentication Bypass by SpoofingCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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.
Attack patterns (CAPEC)
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Web Services API Signature Forgery Leveraging Hash Function Extension WeaknessCAPEC-461High
- Signature SpoofCAPEC-473
- Signature Spoofing by MisrepresentationCAPEC-476likelihood: Low · High
- Session Credential Falsification through PredictionCAPEC-59likelihood: High · High
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- Masquerading: Invalid Code SignatureT1036.001
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls: Code SigningT1553.002
- Adversary-in-the-MiddleT1557
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.