Loading vulnerability…
Nuxt versions before 3.16.0 are susceptible to CDN cache poisoning through crafted requests for Nuxt payload content. A request such as a route with /_payload.json in the query component can cause Nuxt to render a JSON response. When an intervening CDN ignores the query string as part of its cache key, it can cache that JSON response for the normal route and subsequently serve it to visitors. An attacker can repeatedly refresh the poisoned cache entry at the cache-duration interval, sustaining site unavailability.
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.
/?/_payload.json are not cached as equivalent to the base page route. Disable or tightly restrict caching for Nuxt payload/JSON endpoints and dynamic routes where response type can vary based on request structure. Monitor for suspicious requests matching the described pattern and purge affected cache entries if poisoning is detected.Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a Proof-of-Concept (PoC) for CVE-2025-27415, a cache poisoning vulnerability affecting Nuxt3 (versions >=3.0.0 and <3.16.0) when deployed behind a CDN or caching proxy that ignores query strings in cache keys. The repository provides a full docker-compose environment with three main services: a vulnerable Nuxt3 app, an Nginx reverse proxy with caching enabled, and an exploit server written in Python (Flask). The exploit logic is implemented in 'exploit/cache_poisoning.py', which exposes endpoints to start and stop the attack. The attack works by repeatedly sending requests to '/?/_payload.json', causing the CDN/proxy to cache the JSON response at the root path ('/'). As a result, legitimate users accessing '/' receive the poisoned JSON instead of the intended page, resulting in a denial of service. The Nuxt app includes a page ('/ex') to automate and control the attack via a web interface. The repository is well-structured for demonstration and testing of the vulnerability, with clear separation between the vulnerable app, the exploit, and the proxy configuration.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.