Prototype Pollution in the Scheduler component (@progress/kendo-angular-scheduler and @progress/kendo-angular-common) in Progress Software Kendo UI for Angular versions prior to 25.1.0 allows a high-privileged attacker who can control a field path processed by the Scheduler to modify the prototype of built-in objects, resulting in a limited impact on confidentiality, integrity, and availability.
Severity
CVSS 3.1
4.1 medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1321Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution)
Show the promptExplain CVE-2026-106144 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106144?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106144?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106144 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
progress software:kendo ui for angular
Versions
From the CNA's record in the CVE List.
Product
Affected
Progress Software Kendo UI for Angular
from 20.0.0 before 25.1.0
Progress Software Kendo UI for Angular
before 25.1.0
Attack patterns (CAPEC)
CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels Likelihood: High · Severity: Medium
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.