Skip to content

Update dependency vuetify to v3 [SECURITY] - #21

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

Update dependency vuetify to v3 [SECURITY]#21
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-vuetify-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Sep 25, 2022

Copy link
Copy Markdown

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vuetify (source) 2.4.63.0.0 age confidence

Vuetify Cross-site Scripting vulnerability

CVE-2022-25873 / GHSA-q4q5-c5cv-2p68

More information

Details

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.

Severity

  • CVSS Score: 5.4 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Vuetify has a Prototype Pollution vulnerability

CVE-2025-8083 / GHSA-3jp5-5f8r-q2wg

More information

Details

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/ .

Severity

  • CVSS Score: 8.6 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Vuetify has a Cross-site Scripting (XSS) vulnerability in the VDatePicker component

CVE-2025-8082 / GHSA-9w3x-85mw-4fwm

More information

Details

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/ .

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


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

v2.6.4

Compare Source

🔧 Bug Fixes

v2.6.3

Compare Source

🔧 Bug Fixes

v2.6.2

Compare Source

🔧 Bug Fixes

v2.6.1

Compare Source

🔧 Bug Fixes

v2.6.0

Compare Source

v2.6.0 (Horizon)

Welcome to the v2.6.0 release of Vuetify!

🤚 FAQ

  • Where is the upgrade guide?
    • There are no upgrade steps to go from v2.5 to v2.6

💪 Support Vuetify Development

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

💯 Release notes

🔧 Bug Fixes
🚀 Features
v2.6.0.beta.0 - v2.6.0

Includes bugfixes from 2.5.11 to 2.5.14

🚀 Features

v2.5.14

Compare Source

🔧 Bug Fixes

v2.5.13

Compare Source

🔧 Bug Fixes

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 renovate Bot changed the title Update dependency vuetify to v2.6.10 [SECURITY] Update dependency vuetify to v2.6.10 [SECURITY] - autoclosed Feb 24, 2024
@renovate renovate Bot closed this Feb 24, 2024
@renovate
renovate Bot deleted the renovate/npm-vuetify-vulnerability branch February 24, 2024 07:46
@renovate renovate Bot changed the title Update dependency vuetify to v2.6.10 [SECURITY] - autoclosed Update dependency vuetify to v2.6.10 [SECURITY] Feb 24, 2024
@renovate renovate Bot reopened this Feb 24, 2024
@renovate
renovate Bot restored the renovate/npm-vuetify-vulnerability branch February 24, 2024 09:34
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch from d1e7bdd to 2d4aea3 Compare February 24, 2024 09:34
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch from 2d4aea3 to 8a7e524 Compare August 10, 2025 12:36
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch from 8a7e524 to fa76217 Compare September 25, 2025 16:28
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch from fa76217 to 248fad8 Compare October 21, 2025 14:43
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch from 248fad8 to 725a095 Compare March 5, 2026 19:53
@renovate renovate Bot changed the title Update dependency vuetify to v2.6.10 [SECURITY] Update dependency vuetify to v2.6.10 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-vuetify-vulnerability branch March 27, 2026 01:55
@renovate renovate Bot changed the title Update dependency vuetify to v2.6.10 [SECURITY] - autoclosed Update dependency vuetify to v2.6.10 [SECURITY] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch 2 times, most recently from 725a095 to 60e6215 Compare March 30, 2026 22:12
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch from 60e6215 to d80ee17 Compare April 29, 2026 20:12
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch from d80ee17 to 9558772 Compare May 12, 2026 12:31
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch 2 times, most recently from d44f528 to b5dbea2 Compare June 1, 2026 19:49
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch from b5dbea2 to 299a99d Compare July 12, 2026 11:48
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch from 299a99d to 45b13db Compare July 30, 2026 16:58
@renovate
renovate Bot force-pushed the renovate/npm-vuetify-vulnerability branch from 45b13db to accfcba Compare August 26, 2026 17:04
@renovate renovate Bot changed the title Update dependency vuetify to v2.6.10 [SECURITY] Update dependency vuetify to v3 [SECURITY] Aug 26, 2026
@renovate

renovate Bot commented Aug 26, 2026

Copy link
Copy Markdown
Author

⚠️ 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: schoolallocation@1.0.1
npm ERR! Found: vue@2.6.12
npm ERR! node_modules/vue
npm ERR!   vue@"2.6.12" 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-09-03T13_33_00_600Z-debug-0.log

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