CVE-2026-78222 is a NULL pointer dereference vulnerability in the NGINX JavaScript ngx_http_js_module. A malformed HTTP response received through ngx.fetch() can terminate an NGINX worker when trusted JavaScript reads Response.statusText. Exploitation requires attacker control or influence over the fetched HTTP response. The vulnerability affects NGINX JavaScript 0.5.1 through 0.9.9 and 1.0.0 and can cause data-plane denial of service; there is no control-plane exposure.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability referenced by a FreeBSD security-check plugin affecting the angie-module-njs package; the content provides no technical flaw description.
A network-accessible, low-complexity, unauthenticated vulnerability with high impact to availability and no stated confidentiality or integrity impact. The content identifies Debian Linux versions 12.0, 13.0, and 14.0 and libnginx-mod-js as affected.
A vulnerability affecting the njs ngx.fetch functionality, fixed in njs 1.0.1. The provided content does not reliably specify the flaw's impact due to text corruption.
A vulnerability affecting ngx.fetch in njs, fixed in njs 1.0.1. The content does not provide technical impact details.
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.