CVE-2026-106127 · Package
NO FIX YET
The setter utility in @progress/kendo-react-common, used by KendoReact versions 3.5.0 through 16.0.0, lets a high-privileged user who controls a field path modify built-in object prototypes. The sources describe the impact as limited to 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 KendoReact in the affected version range and pass user-controlled field paths to the setter utility, directly or through the Form, Scheduler or Gantt components. The attacker needs high privileges. Apps that do not let users control those field paths are less exposed; the sources do not say more.
Not affected if default-config
Who cares javascript, kendo-react, npm
@progress/kendo-react-common in your lockfile or with npm ls @progress/kendo-react-commonNo fix yet, per the sources.
Prototype Pollution in the setter utility (@progress/kendo-react-common) in Progress Software KendoReact versions 3.5.0 through 16.0.0 allows a high-privileged attacker who can control a field path passed to the utility, directly or through components such as the Form, Scheduler, and Gantt, 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.