Nuxt allows DOS via cache poisoning with payload rendering response

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2025-27415: 0.39% estimated exploitation activity in the next 30 days; percentile 33.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

19 Mar 2025, 19:54 UTC

Last modified by the source

20 Mar 2025, 19:31 UTC

Source last checked

26 Oct 2026, 12:36 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jvhm-gjrh-3h93

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jvhm-gjrh-3h93

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-27415

Advisory: Nuxt allows DOS via cache poisoning with payload rendering response
IDs: CVE-2025-27415, GHSA-jvhm-gjrh-3h93
Record: https://patchnext.com/advisories/cve-2025-27415 (revision 2, source checked 26 Oct 2026, 12:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt 3.16.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt: affected >= 3.0.0, < 3.16.0; fixed in 3.16.0

## Suggested inspection (read-only)
- `npm ls nuxt --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nuxt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jvhm-gjrh-3h93 (OSV record GHSA-jvhm-gjrh-3h93 lists affected ranges: npm nuxt >=3.0.0 <3.16.0 (fixed))
- Verified: https://github.com/advisories/GHSA-jvhm-gjrh-3h93 (GitHub-reviewed advisory GHSA-jvhm-gjrh-3h93 lists affected ranges: npm nuxt >=3.0.0 <3.16.0)

Commands are suggestions: review each one before running it.