Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-42530: HTTP/3 QPACK Use-After-Free in NGINX

Published Jun 17, 2026 · Updated 16 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS9.2Critical · v4
EPSS6.2%94th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
F5
IdentifiersCVE-2026-42530CWE-416 · Use After Free

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-42530The repository contains README.md (278 bytes) and a standalone Python exploit, ep.py (11,137 bytes). The README attributes an unauthenticated HTTP/3 QPACK use-after-free to CVE-2026-42530, lists NGINX 1.31.0 and 1.31.1 as affected, and states that 1.31.2 fixes it; these claims are not independently verified by the supplied material. The script uses asyncio and aioquic, implements QUIC/QPACK encoding helpers, and constructs forged execution-context data using little-endian 64-bit addresses. Its documented attack resets and reopens a QPACK encoder stream, reclaims freed memory with a 1,060-byte POST body, and attempts a GOT overwrite to redirect memcpy to ngx_execute_proc for shell-command execution. Default addresses are memcpy@GOT 0xAB9668 and ngx_execute_proc 0x4B7782, with alternative PIE offsets documented. This is a build-specific, operational-style exploit rather than a detector or framework module, with no visible leak stage or automatic address discovery. The source explicitly ignores --profile and --nginx options in favor of hardcoded configuration. No fixed callback or exfiltration service is visible. The supplied ep.py content is truncated, including the network-stage implementation, so complete protocol behavior and exploit reliability cannot be established. Repository URL, git reference, and archive size were not supplied; empty strings and size 0 represent unavailable metadata, not an empty archive.Udyz · Disclosed Oct 28, 2026 · python · networkOperational
Exposure surface

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.

VendorProductType
F5Nginxapplication
F5Nginx Gateway Fabricapplication
F5Nginx Ingress Controllerapplication
F5Nginx Instance Managerapplication
FAQ

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.
Activity feed

Recent activity

104 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+21 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity68Community discussion across Reddit, Mastodon, and other social sources.