CVE-2025-27415: Nuxt allows DOS via cache poisoning with payload rendering response
Summary
By sending a crafted HTTP request to a server behind an CDN, it is possible in some circumstances to poison the CDN cache and highly impacts the availability of a site.
It is possible to craft a request, such as https://mysite.com/?/payload.json which will be rendered as JSON. If the CDN in front of a Nuxt site ignores the query string when determining whether to cache a route, then this JSON response could be served to future visitors to the site.
Impact
An attacker can perform this attack to a vulnerable site in order to make a site unavailable indefinitely. It is also possible in the case where the cache will be reset to make a small script to send a request each X seconds (=caching duration) so that the cache is permanently poisoned making the site completely unavailable.
Conclusion :
This is similar to a vulnerability in Next.js that resulted in CVE-2024-46982 (and see this article, in particular the "Internal URL parameter and pageProps" part, the latter being very similar to the one concerning us here.)
Other sources
Nuxt is an open-source web development framework for Vue.js. Prior to 3.16.0, by sending a crafted HTTP request to a server behind an CDN, it is possible in some circumstances to poison the CDN cache and highly impacts the availability of a site. It is possible to craft a request, such as https://mysite.com/?/payload.json which will be rendered as JSON. If the CDN in front of a Nuxt site ignores the query string when determining whether to cache a route, then this JSON response could be served to future visitors to the site. An attacker can perform this attack to a vulnerable site in order to make a site unavailable indefinitely. It is also possible in the case where the cache will be reset to make a small script to send a request each X seconds (=caching duration) so that the cache is permanently poisoned making the site completely unavailable. This vulnerability is fixed in 3.16.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/nuxtto a version that resolves this vulnerability.Fixed in 3.16.0 - Upgrade
Upgrade
Nuxtto a version that resolves this vulnerability.Fixed in 3.16.0
Event History
Frequently Asked Questions
What is the severity of CVE-2025-27415?
CVE-2025-27415 has a high severity level due to its potential to poison the CDN cache and affect site availability.
How do I fix CVE-2025-27415?
To fix CVE-2025-27415, upgrade your Nuxt framework to version 3.16.0 or later.
What versions of Nuxt are affected by CVE-2025-27415?
CVE-2025-27415 affects all versions of Nuxt prior to 3.16.0.
What types of attacks are possible with CVE-2025-27415?
CVE-2025-27415 allows for crafted HTTP requests that can poison the CDN cache, impacting site availability.
Is CVE-2025-27415 related to CDN cache issues?
Yes, CVE-2025-27415 specifically involves vulnerabilities that can lead to CDN cache poisoning.