CVE-2025-27415
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNuxt 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA cache poisoning vulnerability in Nuxt versions before 3.16.0 allows attackers to craft requests to `/?/_payload.json` which renders as JSON. When a CDN ignores query strings when determining cache behavior, this JSON response gets cached and served to subsequent visitors, causing denial of service through permanently poisoned cache.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.0.0, < 3.16.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Nuxt versionCheck your package.json file or run 'npm list nuxt' or 'pnpm list nuxt' in your project directory to see the exact version installedAffected if The version is 3.0.0 or higher but lower than 3.16.0
-
Verify the _payload.json endpoint is accessibleMake a GET request to your application's root with the query parameter ?/_payload.json (e.g., https://yourapp.com/?/_payload.json) and check if it returns a JSON responseAffected if The endpoint responds with JSON payload content (typically containing 'payload' or state data)
-
Determine if a CDN or caching layer is in useReview your infrastructure configuration (e.g., Cloudflare, Vercel, AWS CloudFront, nginx caching) to identify if responses are being cached upstream from your applicationAffected if Your application is behind a CDN, reverse proxy, or caching layer that caches HTTP responses
-
Check CDN cache key configuration for query string handlingReview your CDN or proxy cache settings to determine whether query strings are included in cache key calculations (often found in cache key or vary settings)Affected if The CDN is configured to ignore or strip query strings when determining what to cache, meaning different URLs with different query strings share the same cache entry
You are affected if your Nuxt version is 3.0.0 to 3.15.9 and your application serves the _payload.json endpoint while being behind a CDN or proxy that ignores query strings in its cache key decisions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.16.0
Upgrade Nuxt to version 3.16.0 or later, and configure CDN to respect query strings in cache key decisions to prevent cache poisoning.
3.16.0
- Check the current Nuxt version in your project by running `npm list nuxt` or viewing package.json
- Update the Nuxt dependency in package.json to version 3.16.0 or later: `npm install nuxt@^3.16.0` or `yarn add nuxt@^3.16.0` or `pnpm add nuxt@^3.16.0`
- Run the package manager install command to fetch the updated version
- Verify the update was successful by checking the installed version with `npm list nuxt`
- Test your application to ensure the upgrade does not break existing functionality
- If using a CDN in front of your Nuxt site, verify CDN caching configuration to ensure query strings are considered for cache keys
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27415 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27415 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data