CVE-2026-106128 · Package
NO FIX YET
Kendo UI for Vue's shared @progress/kendo-vue-common package lets a high-privileged user who controls a field path, such as one used by the Scheduler, modify built-in object prototypes. The sources describe a limited impact on confidentiality, integrity and availability.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Applications that use Kendo UI for Vue versions 0.4.0 through 9.2.0 and pass field paths that can be influenced by a user with high privileges. The sources do not name a fixed version, so teams should confirm the vendor's patched release before deciding. Applications that do not use this package or do not expose such field paths can skip it.
Not affected if no-user-controlled-field-paths, package-not-installed
Who cares javascript, kendo-ui, vue
@progress/kendo-vue-common is in your dependencies, for example with npm ls @progress/kendo-vue-commonNo fix yet, per the sources.
Prototype Pollution in @progress/kendo-vue-common in Progress Software Kendo UI for Vue versions 0.4.0 through 9.2.0 allows a high-privileged attacker who can control a field path processed by components such as the Scheduler to modify the prototype of built-in objects, resulting in a limited impact on confidentiality, integrity, and availability.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.