Skip to content

fix(deps): update dependency vuetify to v3 [security]#309

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-vuetify-vulnerability
Closed

fix(deps): update dependency vuetify to v3 [security]#309
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-vuetify-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 20, 2026

This PR contains the following updates:

Package Change Age Confidence
vuetify (source) ^2.4.0^3.0.0 age confidence

GitHub Vulnerability Alerts

CVE-2022-25873

The package vuetify from 2.0.0-beta.4 and before 2.6.10 are vulnerable to Cross-site Scripting (XSS) due to improper input sanitization in the 'eventName' function within the VCalendar component.

CVE-2025-8083

The Preset configuration feature of Vuetify is vulnerable to Prototype Pollution due to the internal 'mergeDeep' utility function used to merge options with defaults. Using a specially-crafted, malicious preset can result in polluting all JavaScript objects with arbitrary properties, which can further negatively affect all aspects of the application's behavior. This can lead to a wide range of security issues, including resource exhaustion/denial of service or unauthorized access to data.

If the application utilizes Server-Side Rendering (SSR), this vulnerability could affect the whole server process.

This issue affects Vuetify versions greater than or equal to 2.2.0-beta.2 and less than 3.0.0-alpha.10.

Note:
Version 2.x of Vuetify is End-of-Life and will not receive any updates to address this issue. For more information see here https://v2.vuetifyjs.com/en/about/eol/ .

CVE-2025-8082

Improper neutralization of the title date in the 'VDatePicker' component in Vuetify, allows unsanitized HTML to be inserted into the page. This can lead to a Cross-Site Scripting (XSS) https://owasp.org/www-community/attacks/xss  attack. The vulnerability occurs because the 'title-date-format' property of the 'VDatePicker' can accept a user created function and assign its output to the 'innerHTML' property of the title element without sanitization.

This issue affects Vuetify versions greater than or equal to 2.0.0 and less than 3.0.0.

Note:
Version 2.x of Vuetify is End-of-Life and will not receive any updates to address this issue. For more information see here https://v2.vuetifyjs.com/en/about/eol/ .


Release Notes

vuetifyjs/vuetify (vuetify)

v3.0.0

Compare Source

v3.0.0 (Titan)

Welcome to the v3.0.0 release of Vuetify!

Supporting Vuetify

Vuetify is an open source MIT project that has been made possible due to the generous contributions by sponsors and backers. If you are interested in supporting this project, please consider:

💯 Release notes

🚀 Features
🔧 Bug Fixes

v2.7.2

Compare Source

🔧 Bug Fixes

v2.7.1

Compare Source

🔧 Bug Fixes

v2.7.0

Compare Source

🚀 Features
🔧 Bug Fixes

v2.6.16

Compare Source

🔧 Bug Fixes

v2.6.15

Compare Source

🔧 Bug Fixes

v2.6.14

Compare Source

🔧 Bug Fixes

v2.6.13

Compare Source

🔧 Bug Fixes

v2.6.12

Compare Source

🔧 Bug Fixes

v2.6.11

Compare Source

🔧 Bug Fixes
  • click-outside: remove unused vnode reference (4d3359a)

v2.6.10

Compare Source

🔧 Bug Fixes
🔬 Code Refactoring
  • VSelect: render highlight with vnodes instead of innerHTML (4468e3c)
BREAKING CHANGES
  • VCalendar: eventName function can no longer render arbitrary HTML, convert to VNodes instead.
    eventSummary can no longer be used with v-html, replace with <component :is="{ render: eventSummary }" />

v2.6.9

Compare Source

🔧 Bug Fixes

v2.6.8

Compare Source

🔧 Bug Fixes

v2.6.7

Compare Source

🔧 Bug Fixes

v2.6.6

Compare Source

🔧 Bug Fixes
🔬 Code Refactoring

Configuration

📅 Schedule: Branch creation - "" in timezone America/Vancouver, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from Jxio, ochiu and seeker25 as code owners February 20, 2026 15:53
@renovate
Copy link
Contributor Author

renovate bot commented Feb 20, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: pay-ui@1.3.34
npm ERR! Found: vue@2.7.16
npm ERR! node_modules/vue
npm ERR!   peer vue@"^2.6.11" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vue@"^3.5.0" from vuetify@3.12.0
npm ERR! node_modules/vuetify
npm ERR!   vuetify@"^3.0.0" from the root project
npm ERR!   peer vuetify@">=3" from vite-plugin-vuetify@2.1.3
npm ERR!   node_modules/vite-plugin-vuetify
npm ERR!     peerOptional vite-plugin-vuetify@">=2.1.0" from vuetify@3.12.0
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-02-20T15_53_29_394Z-debug-0.log

@seeker25 seeker25 closed this Feb 20, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Feb 20, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/npm-vuetify-vulnerability branch February 20, 2026 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant