Prototype Pollution in Progress Software Kendo UI for Angular
- Exploited
- No known exploitation
- Fix
- Fixed in 25.1.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 25.1.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The Scheduler component in Progress Software Kendo UI for Angular (the @progress/kendo-angular-scheduler and @progress/kendo-angular-common packages) has a prototype pollution flaw. An attacker reaches it remotely over the network, but only after logging in with high-privilege access, and it lets them change the prototype of built-in objects, with limited effects on confidentiality, integrity, and availability.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects npm packages
- Severity4.1/10CVSS 4.1
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 25.1.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- @progress/kendo-angular-commonnpm
From 20.0.0 · fixed in 25.1.0
- @progress/kendo-angular-schedulernpm
fixed in 25.1.0
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-106144
Is CVE-2026-106144 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-106144?
@progress/kendo-angular-common (npm): from 20.0.0 before 25.1.0. @progress/kendo-angular-scheduler (npm): before 25.1.0.Source: cve.now feed data
How do I fix CVE-2026-106144?
Upgrade to a fixed version: 25.1.0.Source: cve.now feed data