Repository navigation
🚨 [security] Update nuxt 2.12.2 → 4.6.2 (major) - #163
Open
depfu[bot] wants to merge 1 commit into
Open
depfu[bot] wants to merge 1 commit into
depfu[bot] wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ nuxt (2.12.2 → 4.6.2) · Repo
Security Advisories 🚨
🚨 Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routes
🚨 Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `` when `pages` is disabled
🚨 Nuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitive
🚨 Nuxt server islands render `useHeadSafe` input without sanitisation
🚨 Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routes
🚨 Nuxt dev server discloses project root and workspace UUID via the Chrome DevTools workspace endpoint
🚨 Nuxt dev server discloses project root and workspace UUID via the Chrome DevTools workspace endpoint
🚨 Nuxt: Unauthenticated CPU exhaustion parsing and hashing the Nuxt island endpoint body before hash validation
🚨 Nuxt: Unauthorized Component Instantiation via Server Island Props
🚨 Nuxt: Server-Side Remote Code Execution via Runtime Template Injection in Nuxt Server Island Props
🚨 Nuxt: Unauthenticated CPU exhaustion parsing and hashing the Nuxt island endpoint body before hash validation
🚨 Nuxt: Unauthenticated out-of-memory crash via unbounded v-for expansion in island rendering
🚨 Nuxt route rules silently dropped for mixed-case paths, bypassing appMiddleware auth gates (incomplete fix for CVE-2026-53721)
🚨 Nuxt route rules silently dropped for mixed-case paths, bypassing appMiddleware auth gates (incomplete fix for CVE-2026-53721)
🚨 Nuxt: Unauthenticated out-of-memory crash via unbounded v-for expansion in island rendering
🚨 Nuxt: Unauthorized Component Instantiation via Server Island Props
🚨 Nuxt: Server-Side Remote Code Execution via Runtime Template Injection in Nuxt Server Island Props
🚨 Nuxt runtime payload cache discloses another user's SSR data across users and to unauthenticated clients
🚨 Cross-site scripting via slot content in Nuxt's head components
🚨 Nuxt: URL-handling weaknesses in `navigateTo` and `reloadNuxtApp`: SSR open redirect, client-side script execution via the `open` option, and protocol-relative bypass in `reloadNuxtApp`
🚨 Nuxt dev server vite-node IPC socket is world-connectable on Linux
🚨 Nuxt: URL-handling weaknesses in `navigateTo` and `reloadNuxtApp`: SSR open redirect, client-side script execution via the `open` option, and protocol-relative bypass in `reloadNuxtApp`
🚨 Nuxt: Reflected XSS in `` via unsanitised `javascript:` or `data:` URL
🚨 Nuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher
🚨 Nuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher
🚨 Nuxt dev server vite-node IPC socket is world-connectable on Linux
🚨 Cross-site scripting via slot content in Nuxt's head components
🚨 Nuxt: Reflected XSS in `` via unsanitised `javascript:` or `data:` URL
🚨 Nuxt: Dev server discloses project absolute path and persistent workspace UUID via `/.well-known/appspecific/com.chrome.devtools.json`
🚨 Nuxt's route middleware is not enforced when rendering `.server.vue` pages via `/__nuxt_island/page_*`
🚨 Nuxt's route middleware is not enforced when rendering `.server.vue` pages via `/__nuxt_island/page_*`
🚨 Nuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoning
🚨 Nuxt: Reflected XSS in `navigateTo()` external redirect
🚨 Nuxt: Reflected XSS in `navigateTo()` external redirect
🚨 Nuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoning
🚨 Nuxt has Client-Side Path Traversal in Nuxt Island Payload Revival
🚨 Nuxt has Client-Side Path Traversal in Nuxt Island Payload Revival
🚨 Nuxt allows DOS via cache poisoning with payload rendering response
🚨 Nuxt vulnerable to remote code execution via the browser when running the test locally
🚨 nuxt vulnerable to Cross-site Scripting in navigateTo if used after SSR
🚨 nuxt Code Injection vulnerability
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands