CVE-2026-106156: Progress Software Telerik UI for ASP.NET Core · Uncontrolled Resource Consumption
Affects Progress Software Telerik UI for ASP.NET CoreSource CVE Database V5
Not known to be exploited · CVSS 8.6 High : upgrade to 2026.3.1015 soon.
Data as of 11 Nov 2026, 17:35 UTC
Thin evidence
One scorer or none| CNA (ProgressSoftware) | CVSS 3.1 | 8.6 |
|---|
- Patch
- Available – fixed in 2026.3.1015
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade Progress Software Telerik UI for ASP.NET Core to 2026.3.1015.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Progress SoftwareTelerik UI for ASP.NET Core | Affected
| Fixed in
|
AI-suggested
Upgrade Telerik UI for ASP.NET Core to version 2026.3.1015 or later, where this vulnerability is fixed. Until the upgrade, ensure that aggregation endpoints are not exposed without authentication or proper access controls to prevent exploitation.
Description
CVE-2026-106156 is a high-severity vulnerability in Progress Software Telerik UI for ASP.NET Core versions 2015.1.318 through 2026.3.811. It involves uncontrolled resource consumption due to repeated server-side aggregation requests causing dynamic assemblies and load contexts to accumulate, leading to increased memory usage. An unauthenticated remote attacker can exploit this if an aggregation endpoint is exposed without authentication, potentially exhausting system resources and impacting application availability. The issue is fixed in version 2026.3.1015.