Skip to content

Comments

Update dependency vuetify to v3 [SECURITY]#548

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-vuetify-vulnerability
Open

Update dependency vuetify to v3 [SECURITY]#548
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-vuetify-vulnerability

Conversation

@renovate
Copy link

@renovate renovate bot commented Sep 25, 2022

This PR contains the following updates:

Package Change Age Confidence
vuetify (source) 2.6.43.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

v2.6.5

Compare Source

🔧 Bug Fixes

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.


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

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

@renovate
Copy link
Author

renovate bot commented Sep 25, 2022

⚠ 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 could not resolve
npm ERR! 
npm ERR! While resolving: sass-loader@10.2.1
npm ERR! Found: node-sass@7.0.0
npm ERR! node_modules/node-sass
npm ERR!   dev node-sass@"7.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional node-sass@"^4.0.0 || ^5.0.0 || ^6.0.0" from sass-loader@10.2.1
npm ERR! node_modules/sass-loader
npm ERR!   dev sass-loader@"10.2.1" from the root project
npm ERR!   sass-loader@"^10.2.0" from @nuxtjs/vuetify@1.12.3
npm ERR!   node_modules/@nuxtjs/vuetify
npm ERR!     dev @nuxtjs/vuetify@"1.12.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: node-sass@6.0.1
npm ERR! node_modules/node-sass
npm ERR!   peerOptional node-sass@"^4.0.0 || ^5.0.0 || ^6.0.0" from sass-loader@10.2.1
npm ERR!   node_modules/sass-loader
npm ERR!     dev sass-loader@"10.2.1" from the root project
npm ERR!     sass-loader@"^10.2.0" from @nuxtjs/vuetify@1.12.3
npm ERR!     node_modules/@nuxtjs/vuetify
npm ERR!       dev @nuxtjs/vuetify@"1.12.3" from the root project
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 /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-09-25T18_23_53_420Z-debug-0.log

@renovate renovate bot changed the title Update dependency vuetify to 2.6.10 [SECURITY] Update dependency vuetify to v2.6.10 [SECURITY] Mar 23, 2023
@renovate renovate bot changed the title Update dependency vuetify to v2.6.10 [SECURITY] Update dependency vuetify to v2.6.10 [SECURITY] - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/npm-vuetify-vulnerability branch December 8, 2024 18:51
@renovate renovate bot changed the title Update dependency vuetify to v2.6.10 [SECURITY] - autoclosed Update dependency vuetify to v2.6.10 [SECURITY] Dec 8, 2024
@renovate renovate bot reopened this Dec 8, 2024
@renovate renovate bot force-pushed the renovate/npm-vuetify-vulnerability branch from 9a63d9a to 9772980 Compare December 8, 2024 22:14
@renovate
Copy link
Author

renovate bot commented Dec 8, 2024

⚠️ 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: scroll-icon-generator@0.1.0
npm ERR! Found: vue@2.6.14
npm ERR! node_modules/vue
npm ERR!   vue@"2.6.14" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vue@"^3.2.0" from vuetify@3.0.0
npm ERR! node_modules/vuetify
npm ERR!   vuetify@"3.0.0" from the root project
npm ERR!   peer vuetify@"^3.0.0-beta.4" from vite-plugin-vuetify@1.0.2
npm ERR!   node_modules/vite-plugin-vuetify
npm ERR!     peerOptional vite-plugin-vuetify@"^1.0.0-alpha.12" from vuetify@3.0.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-18T17_39_53_002Z-debug-0.log

@renovate renovate bot force-pushed the renovate/npm-vuetify-vulnerability branch from 9772980 to 2421849 Compare August 10, 2025 14:24
@renovate renovate bot force-pushed the renovate/npm-vuetify-vulnerability branch from 2421849 to fc7e457 Compare December 12, 2025 23:09
@renovate renovate bot changed the title Update dependency vuetify to v2.6.10 [SECURITY] Update dependency vuetify to v3 [SECURITY] Dec 12, 2025
@renovate renovate bot changed the title Update dependency vuetify to v3 [SECURITY] Update dependency vuetify to v3 [SECURITY] - autoclosed Feb 18, 2026
@renovate renovate bot closed this Feb 18, 2026
@renovate renovate bot changed the title Update dependency vuetify to v3 [SECURITY] - autoclosed Update dependency vuetify to v3 [SECURITY] Feb 18, 2026
@renovate renovate bot reopened this Feb 18, 2026
@renovate renovate bot force-pushed the renovate/npm-vuetify-vulnerability branch 2 times, most recently from fc7e457 to 917c55c Compare February 18, 2026 17:40
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.

0 participants