CVE-2025-27415: Nuxt Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-jvhm-gjrh-3h93
Share
CVSS 7.5
CWE-349
Published
Advisory Summary

CVE-2025-27415 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data) affecting Nuxt libraries in the npm ecosystem. The issue involves nuxt allows dos via cache poisoning with payload rendering response. Remediation is available by upgrading affected packages to version 3.16.0.

CVE-2025-27415 at a Glance

CVE Identifier CVE-2025-27415
GHSA Identifier GHSA-jvhm-gjrh-3h93
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data
Affected Product Nuxt
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2025-27415

To remediate this vulnerability, upgrade all affected Nuxt dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nuxt fixed: 3.16.0 
npm install nuxt@3.16.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls nuxt

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-27415, inspect your project dependencies using npm:

npm ls nuxt

Analyze the terminal output to locate any version of Nuxt in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.16.0), your application is affected.

Note: The npm ls nuxt command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data, where the product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted. In Nuxt, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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](https://zhero-web-sec.github.io/research-and-things/nextjs-cache-and-chains-the-stale-elixir), in particular the "Internal URL parameter and pageProps" part, the latter being very similar to the one concerning us here.)

CVE-2025-27415 Affected Nuxt Versions

1 component(s)
Fixed Versions:
3.16.0
Product / Package Ecosystem Affected Versions Fixed Version
nuxt
npm/nuxt
npm
≥ 3.0.0
< 3.16.0
3.16.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/nuxt/nuxt/security/advisories/GHSA-jvhm-gjrh-3h93
NVD — CVE-2025-27415 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-27415
Nuxt Source Repository REPOSITORY
https://github.com/nuxt/nuxt

Frequently Asked Questions

What is CVE-2025-27415?
CVE-2025-27415 is a security vulnerability in Nuxt involving Nuxt allows DOS via cache poisoning with payload rendering response under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data.
Which Nuxt versions are affected?
Affected versions include releases prior to 3.16.0 across affected packages: nuxt.
What version fixes CVE-2025-27415?
Upgrading to 3.16.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nuxt affected?
Yes, nuxt is affected in releases prior to 3.16.0. Upgrade your dependency to 3.16.0 or later.
What is the CVSS score of CVE-2025-27415?
CVE-2025-27415 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2025-27415?
CVE-2025-27415 is classified under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data (The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.).
How can I check npm dependencies for CVE-2025-27415?
Run the dependency tree command: 'npm ls nuxt'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jvhm-gjrh-3h93",
  "modified" : "2025-03-20T19:31:04Z",
  "published" : "2025-03-19T19:54:25Z",
  "aliases" : [ "CVE-2025-27415" ],
  "summary" : "Nuxt allows DOS via cache poisoning with payload rendering response",
  "details" : "### Summary\n\nBy 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.\n\nIt 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.\n\n### Impact\n\nAn 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.\n\n\n## Conclusion : \n\nThis is similar to a vulnerability in Next.js that resulted in CVE-2024-46982 (and see [this article](https://zhero-web-sec.github.io/research-and-things/nextjs-cache-and-chains-the-stale-elixir), in particular the \"Internal URL parameter and pageProps\" part, the latter being very similar to the one concerning us here.)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "nuxt"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.16.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nuxt/nuxt/security/advisories/GHSA-jvhm-gjrh-3h93"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-27415"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nuxt/nuxt"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-349" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-03-19T19:54:25Z",
    "nvd_published_at" : "2025-03-19T19:15:47Z"
  }
}