🚨 [security] Update vue-router 4.6.4 → 5.2.0 (major)

[depfu]

---

🚨 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?

✳️ vue-router (4.6.4 → 5.2.0) · Repo

Release Notes

5.2.0

   🚀 Features

• Add helpful diagnostics  -  by @posva in #2737 (628fe)

   🐞 Bug Fixes

• Allow pinia 4  -  by @posva (16535)
• scroll: Ignore stale async scrollBehavior results  -  by @baozjj and @cursoragent in #2730 (303df)
• unplugin: Reject invalid hex digits in [x+hh] character codes  -  by @greymoth-jp in #2744 (4d967)

    View changes on GitHub

5.1.0

   🚀 Features

• Typed definePage params.path  -  by @posva in #2716 (d65de)
• Strict type for definePage param default  -  by @posva (0ae10)
• Support raw param parsers  -  by @posva (eadec)
• Force array type raw param parsers  -  by @posva (7a68b)
• Allow overriding the global Router type  -  by @posva (1cd93)
• Emit runtime warning for invalid format in query params  -  by @posva (8259a)
• Override useRouter() return with experimental types config  -  by @posva (39a34)
• Allow string as a param parser for convenience  -  by @posva (be37b)

   🐞 Bug Fixes

• Fix auto import fixes and make experimental esm only  -  by @posva (db3a6)
• Deterministic param parser types order  -  by @posva (bf0fc)
• Avoid importing unused param parsers  -  by @posva (41c00)
• Filter invalid query params without failing to match  -  by @posva (db717)
• Detect not set format  -  by @posva (aa89e)
• Allow undefined values for params in query  -  by @posva (4726e)
• experimental: Repeatable params in subsegments  -  by @posva (84664)
• types: Add vite as optional peer dependency  -  by @ForgottenR, @posva and shihuijie in #2712 (facbf)

    View changes on GitHub

5.0.7

   🚀 Features

• Upgrade to babel 8  -  by @posva (8d3e6)
• Make defineParamParser() more intuitive  -  by @posva (8715b)
• Upgrade @vue/devtools-api  -  by @posva (87c3a)
• matcher: Hint at params: {} workaround in discarded params warning  -  by @posva and shanliuling in #2689 (c2b13)
• param-parsers: Add include/exclude options  -  by @posva (91cde)

   🐞 Bug Fixes

• matcher:
  • Finalize param token before processing escaped colon  -  by @babu-ch and @posva in #2654 (20521)
• query:
  • Use Object.create(null) to prevent prototype pollution  -  by @wdskuki, wdsmini and @posva in #2661 (be88c)
• resolve:
  • Omit empty optional params from resolved params  -  by @babu-ch and @posva in #2434 (1ef09)
• types:
  • Wire RouteNamedMap via generated routes.d.ts  -  by @posva in #2700 (aef99)
• unplugin:
  • Avoid generating empty routes  -  by @FrontEndDog and @posva in #2642 (10a8b)
  • Apply definePage path-param parser overrides  -  by @posva in #2699 (c8074)
• volar:
  • Drop runtime @vue/language-core import  -  by @danielroe in #2710 (8af50)

    View changes on GitHub

5.0.6

   🐞 Bug Fixes

• Missing closing quote in generated import  -  by @zjy040525 and @posva in #2688 (32f78)

    View changes on GitHub

5.0.5

   🚀 Features

• Enable standard schema param parsers  -  by @posva (ea8e3)
• Normalize param parsers once  -  by @posva (48087)

   🐞 Bug Fixes

• Track definePage imports per-file to fix named view race condition  -  by @posva (11191)
• Avoid double decoding hash on string location  -  by @posva (1578c)

    View changes on GitHub

5.0.4

   🐞 Bug Fixes

• Avoid iterator helpers for Node 20 compat  -  by @cwandev in #2635 (47130)
• Escape backslahes in string literals  -  by @posva (71fdb)
• Avoid false duplicate route warning for named views  -  by @posva (72012)
• Allow pushing to auto routes  -  by @posva (47f03)
• loaders: Restore context in sequential awaits  -  by @posva (fce5d)

    View changes on GitHub

5.0.3

   🚨 Breaking Changes

• experimental:
  • Make miss() throw internally and return never  -  by @posva (077e1)
  • Add reroute() and deprecate NavigationResult  -  by @posva (308db)
  • Remove selectNavigationResult  -  by @posva (9e88a)

   🚀 Features

• Support _parent in nested folders  -  by @posva (0a37f)
• Warn on _parent conflict  -  by @posva (182fe)
• Set _parent as non matchable by default  -  by @posva (8f91c)
• Warn on conflicting components for routes  -  by @posva (34ace)
• Use type module  -  by @posva (dc9ff)
• Add deprecation warning for next() callback in navigation guards  -  by @posva (797f5)
• Extract alias from definePage  -  by @posva (835df)
• Display aliases in logs  -  by @posva (7aa60)
• Deprecate new NavigationResult(to) in favor of reroute(to)  -  by @posva (382e3)
• experimental:
  • Handle aliasOf in resolvers  -  by @posva (8fe45)
  • Generate aliases from override in resolver  -  by @posva (a00ac)
  • Warn against non absolute aliases  -  by @posva (476c6)

   🐞 Bug Fixes

• Avoid non matchable routes in auto-routes  -  by @posva (48649)
• Handle quotes in d.ts  -  by @posva (d7764)
• Avoid route entry in map for _parent  -  by @posva (1dfcc)
• Handle nested groups  -  by @posva (4a4be)
• Stable route ordering for group folders with same path  -  by @posva (1db94)
• Correct route ordering for group nodes with inflated scores  -  by @posva (515f4)
• Cleanup old route overrides  -  by @posva (b28a7)
• Remove name from _parent.vue files  -  by @posva (6e8f1)
• ci:
  • Format sponsor files before change detection  -  by @posva (f68d6)
  • Use manual git commit in update-sponsors  -  by @posva (8ee99)
• experimental:
  • Resolve TS errors in resolver/router type hierarchy  -  by @posva (a86f1)
• types:
  • Relax RouteMapGeneric constraint for interface-based RouteNamedMap  -  by @YevheniiKotyrlo in #2624 (cdf7b)
• volar:
  • Use ts.getTokenPosOfNode instead of node.getStart  -  by @KazariEX in #2630 (0b050)

   🏎 Performance

• Avoid merging empty object in record  -  by @posva (4213e)

    View changes on GitHub

5.0.2

   🐞 Bug Fixes

• Remove devtools from iife build  -  by @posva (58c03)
• Loose version check vue-router  -  by @posva (90e4b)
• volar: Empty options  -  by @posva (02275)

    View changes on GitHub

5.0.0

Vue Router 5 is a boring release, it merges unplugin-vue-router into the core package with no breaking changes. The only exception is that the iife build no longer includes @vue/devtools-api because it has been upgraded to v8 and does not expose an IIFE build itself. You can track that change in this issue. See the migration guide for instructions on how to upgrade from unplugin-vue-router to Vue Router 5.

   🚀 Features

• experimental: Query params are optional by default  -  by @posva (78913)
• Add volar plugins  -  by @posva (530ac)
• Add data loaders as experimental  -  by @posva (ab895)
• Add route json schema  -  by @posva (20675)
• Upgrade devtools-api to v7  -  by @posva (17b84)
• Upgrade devtools to v8  -  by @posva (b8aa2)
• Runtime error on missing param parsers  -  by @posva (3444b)
• volar: Allow rootDir option  -  by @posva (df65a)

   🐞 Bug Fixes

• Avoid breaking older browsers support  -  by @posva (c7ba4)
• Trigger navigation guards when keep-alive component is reactivated for different route  -  by @babu-ch and @posva in #2604 (c7735)
• Add automatic types for param parsers  -  by @posva (0fb5d)
• Param parsers when dts is not at root  -  by @posva (16b39)
• Expose resolveOptions for unplugin  -  by @posva (35543)
• Escape tildes in paths  -  by @posva (aac2e)
• volar: Upgrade config read  -  by @posva (e3024)

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ yaml (indirect, 2.8.2 → 2.9.0) · Repo

Security Advisories 🚨

🚨 yaml is vulnerable to Stack Overflow via deeply nested YAML collections

Parsing a YAML document with yaml may throw a RangeError due to a stack overflow.

The node resolution/composition phase uses recursive function calls without a depth bound. An attacker who can supply YAML for parsing can trigger a RangeError: Maximum call stack size exceeded with a small payload (~2–10 KB). The RangeError is not a YAMLParseError, so applications that only catch YAML-specific errors will encounter an unexpected exception type. Depending on the host application's exception handling, this can fail requests or terminate the Node.js process.

Flow sequences allow deep nesting with minimal bytes (2 bytes per level: one [ and one ]). On the default Node.js stack, approximately 1,000–5,000 levels of nesting (2–10 KB input) exhaust the call stack. The exact threshold is environment-dependent (Node.js version, stack size, call stack depth at invocation).

Note: the library's Parser (CST phase) uses a stack-based iterative approach and is not affected. Only the compose/resolve phase uses actual call-stack recursion.

All three public parsing APIs are affected: YAML.parse(), YAML.parseDocument(), and YAML.parseAllDocuments().

PoC

const YAML = require('yaml');
// ~10 KB payload: 5000 levels of nested flow sequences

const payload = '['.repeat(5000) + '1' + ']'.repeat(5000);
try {

YAML.parse(payload);

} catch (e) {

console.log(e.constructor.name); // RangeError (NOT YAMLParseError)

console.log(e.message);          // Maximum call stack size exceeded

}

Test environment: Node.js v24.12.0, macOS darwin arm64

Version	Nesting Depth	Input Size	Result
1.0.0	5,000	10,001 B	RangeError
1.10.2	5,000	10,001 B	RangeError
2.0.0	5,000	10,001 B	RangeError
2.8.2	5,000	10,001 B	RangeError
2.8.3	5,000	10,001 B	YAMLParseError

Depth threshold on yaml 2.8.2:

Nesting Depth	Input Size	Result
500	1,001 B	Parses successfully
1,000	2,001 B	RangeError (threshold varies by stack size)
5,000	10,001 B	RangeError

Release Notes

2.9.0

The changes here are really only patches, but I'm releasing this as a minor version to note a small change to the documentation of parseDocument() and parseAllDocuments(): I've removed the claim that they'll "never throw".

It remains the case that practically all non-malicious inputs will be handled without emitting an error, but there is a decent chance that code paths remain where e.g. a RangeError due to call stack exhaustion can be triggered by malicious inputs. Up to now, I've considered these as security vulnerabilities, and in fact it's the only category of error for which yaml CVEs have been issued so far.

Starting from this release, I'll be considering such errors as bugs, but not vulnerabilities. I do welcome people and/or LLMs looking for them, but please report them as normal issues rather than suspected security vulnerabilities. This also applies to previously undiscovered bugs in earlier releases.

• fix: Avoid calling Array.prototype.push.apply() with large source array
• fix(lexer): Avoid recursive calls that may exhaust the call stack

2.8.4

• Disable alias resolution with maxAliasCount:0 (#677)
• Handle invalid unicode escapes (e1a1a77)
• Apply minFractionDigits only to decimal strings (#676)

2.8.3

• Add trailingComma ToString option for multiline flow formatting (#670)
• Catch stack overflow during node composition (1e84ebb)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 19 commits:

• 2.9.0
• docs: Clarify that not all errors can be avoided
• fix: Avoid calling Array.prototype.push.apply() with large source array
• fix(lexer): Avoid recursive calls that may exhaust the call stack
• 2.8.4
• fix: Disable alias resolution with maxAliasCount:0 (#677)
• fix: Handle invalid unicode escapes
• style: Satify Prettier
• fix: Apply minFractionDigits only to decimal strings (#676)
• chore: Bump JSR version to v2.8.3 (#673)
• docs: Add trailingComma ToString option
• 2.8.3
• fix: Catch stack overflow during node composition
• ci: Include Prettier check in lint action
• chore: Refresh lockfile
• Add trailingComma ToString option for multiline flow formatting (#670)
• ci: Drop the branch filter from GitHub PR actions
• chore: Update docs-slate
• chore: Update docs-slate

🆕 @​types/jsesc (added, 2.5.1)

🆕 @​vue-macros/common (added, 3.1.4)

🆕 ast-kit (added, 2.2.0)

🆕 ast-walker-scope (added, 0.9.0)

🆕 confbox (added, 0.2.4)

🆕 confbox (added, 0.1.8)

🆕 exsolve (added, 1.1.1)

🆕 local-pkg (added, 1.2.1)

🆕 magic-string-ast (added, 1.0.3)

🆕 mlly (added, 1.8.2)

🆕 pkg-types (added, 1.3.1)

🆕 pkg-types (added, 2.3.1)

🆕 muggle-string (added, 0.4.1)

🆕 quansync (added, 0.2.11)

🆕 scule (added, 1.3.0)

🆕 ufo (added, 1.6.4)

🆕 unplugin (added, 3.3.0)

🆕 webpack-virtual-modules (added, 0.6.2)

🆕 @​babel/generator (added, 8.0.0)

🆕 @​babel/helper-string-parser (added, 8.0.0)

🆕 @​babel/helper-validator-identifier (added, 8.0.4)

🆕 @​babel/parser (added, 8.0.4)

🆕 @​babel/types (added, 8.0.4)

🆕 chokidar (added, 5.0.0)

🆕 readdirp (added, 5.1.1)

🗑️ @​vue/devtools-api (removed)

---

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

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)