CVE-2026-42530 is a use-after-free vulnerability in NGINX Open Source's HTTP/3 QUIC implementation, specifically ngx_http_v3_module. A specially crafted HTTP/3 session can cause a QPACK encoder stream to be reopened after it has been closed and its associated memory freed. Subsequent processing dereferences the freed memory in an NGINX worker process, causing memory corruption.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 4 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
99 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific CVE listed among vulnerabilities described as weaponized and accompanied by public proof-of-concept code in the actors' toolset.
A specific CVE referenced as weaponized within the actors' toolset; the content does not describe the flaw type or affected product.
An nginx HTTP/3 use-after-free vulnerability for which the actor used a cloned public proof of concept during a partial trial.
A use-after-free vulnerability in NGINX's HTTP/3 module reachable remotely without authentication via the QPACK encoder stream.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.