chore(deps): update dependency nuxt to v3.19.0 [security] #42
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.
Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.
This PR contains the following updates:
3.18.1
->3.19.0
GitHub Vulnerability Alerts
CVE-2025-59414
Summary
A client-side path traversal vulnerability in Nuxt's Island payload revival mechanism allowed attackers to manipulate client-side requests to different endpoints within the same application domain when specific prerendering conditions are met.
Technical Details
The vulnerability occurs in the client-side payload revival process (revive-payload.client.ts) where Nuxt Islands are automatically fetched when encountering serialized
__nuxt_island
objects. The issue affects the following flow:__nuxt_island
objectdevalue.stringify
and stored in the prerendered pagedevalue.parse
deserializes the payload/__nuxt_island/${key}.json
wherekey
could contain path traversal sequencesPrerequisites for Exploitation
This vulnerability requires all of the following conditions:
nitro.prerender
)useFetch
,useAsyncData
, or similar composablesAttack Scenario
This could cause the client to make requests to
/__nuxt_island/../../../../internal/service.json
if path traversal is not properly handled by the server.Impact Assessment
Mitigation
Action Required:
Temporary Workarounds (if immediate update is not possible):
Fix Details
The fix implemented validation for Island keys in
revive-payload.server.ts
:/^[a-z][a-z\d-]*_[a-z\d]+$/i
Release Notes
nuxt/nuxt (nuxt)
v3.19.0
Compare Source
👀 Highlights
Please see the release notes for Nuxt v4.1 for full details on the features and fixes in Nuxt v3.19.
✅ Upgrading
As usual, our recommendation for upgrading is to run:
This will refresh your lockfile and pull in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.
👉 Changelog
compare changes
🚀 Enhancements
ignore
option toresolveFiles
(#32858)onInstall
andonUpgrade
module hooks (#32397)rolldown-vite
(#31812)defineRouteRules
to pagerules
property (#32897)getLayerDirectories
util and refactor to use it (#33098)🔥 Performance
🩹 Fixes
satisfies
in page augmentation (#32902)useFetch
hooks (#32891)resolvePath
and normalize file extensions (#32857)requestTimeout
+ allow configuration (#32874)node_modules/
if no customsrcDir
(#32987)route
object (#32899)defineNuxtModule().with()
(#33081)nuxtApp._runningTransition
on resolve (#33025)💅 Refactors
async/await
inafterEach
(#32999)📖 Documentation
setupTimeout
and addteardownTimeout
(#32868)--nightly
command (#32907)useRoute
and accessing route in middleware (#33004)🏡 Chore
type: 'module'
in playground (#33099)✅ Tests
import.meta.dev
(#33023)findWorkspaceDir
rather than relative paths to repo root (c4c3ada96)expect.poll
(f4354203a)expect.poll
instead ofexpectWithPolling
(15ca5be95)vi.waitUntil
instead of custom retry logic (4c8c13090)🤖 CI
❤️ Contributors
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.