CVE-2026-42530: HTTP/3 QPACK Use-After-Free in NGINX
- Vendor
- F5
CVE-2026-42530 is a use-after-free vulnerability in the ngx_http_v3_module HTTP/3 implementation in NGINX Open Source 1.31.0 and 1.31.1. When HTTP/3 over QUIC is enabled, a remote unauthenticated attacker can use a specially crafted HTTP/3 session to reopen a QPACK encoder stream after its associated memory has been freed. Under additional conditions beyond the attacker's control, processing the reopened stream can cause a worker process to access freed memory and restart. Arbitrary code execution is also possible if Address Space Layout Randomization (ASLR) is disabled or bypassed.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Exploitation can crash and restart NGINX worker processes, disrupting request handling and potentially causing denial of service. If ASLR is disabled or successfully bypassed, exploitation may permit arbitrary code execution with the privileges of the affected worker process, compromising data and services accessible to that process.
Mitigation
If you can’t patch tonight, do this now.
Disable HTTP/3 by removing the quic parameter from all NGINX listen directives while retaining HTTPS over TCP where required. Restrict access to QUIC listeners if HTTP/3 cannot immediately be disabled. Ensure ASLR is enabled to reduce code-execution risk; ASLR does not prevent the underlying use-after-free or denial of service. Monitor for repeated worker crashes and restarts.
Remediation
Patch, then assume compromise.
Upgrade affected NGINX Open Source installations to version 1.31.2 or a later supported release containing the fix. Update downstream products and packages embedding the vulnerable NGINX component; identified fixed releases include NGINX Gateway Fabric 2.6.4, NGINX Ingress Controller 5.5.1, NGINX Buildpack 1.2.91, and Staticfile Buildpack 1.6.91. End-of-Technical-Support versions were not evaluated and should be replaced with supported, fixed releases.
Exploits
1 exploit validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-42530 exploited in the wild?
- Yes. As of Nov 3, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-42530?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-42530, the earliest disclosed Oct 28, 2026.
- Is there a patch for CVE-2026-42530?
- Upgrade affected NGINX Open Source installations to version 1.31.2 or a later supported release containing the fix. Update downstream products and packages embedding the vulnerable NGINX component; identified fixed releases include NGINX Gateway Fabric 2.6.4, NGINX Ingress Controller 5.5.1, NGINX Buildpack 1.2.91, and Staticfile Buildpack 1.6.91.
- What products are affected by CVE-2026-42530?
- F5 Nginx, F5 Nginx Gateway Fabric, F5 Nginx Ingress Controller, and F5 Nginx Instance Manager.
- How severe is CVE-2026-42530?
- CVE-2026-42530 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 6.2% (94th percentile) as of Nov 3, 2026.
Recent activity
104 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.