CVE-2026-106154: Progress Software Telerik UI for ASP.NET Core · Uncontrolled Recursion
Affects Progress Software Telerik UI for ASP.NET CoreSource CVE Database V5
Not known to be exploited · CVSS 8.6 High · fixed in 2026.4.1111 : patch Progress Software Telerik UI for ASP.NET Core soon.
Data as of 12 Nov 2026, 17:35 UTC
Thin evidence
One scorer or none| CNA (ProgressSoftware) | CVSS 3.1 | 8.6 |
|---|
- Patch
- Available – fixed in 2026.4.1111
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 12 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 12 Nov 2026.
What to do
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.4.1111 or later, where this vulnerability is fixed. If you cannot patch yet, restrict access to endpoints using DataSourceRequest model binding to authenticated and authorized users to reduce exposure.
Description
CVE-2026-106154 is a high-severity vulnerability in Progress Software's Telerik UI for ASP.NET Core affecting versions from 2015.1.318 through 2026.3.1015. It involves uncontrolled recursion in the server-side FilterParser when processing nested filter expressions without a recursion-depth limit, combined with the FilterLexer lacking input-length limits. An unauthenticated remote attacker can exploit this by sending deeply nested filters to an exposed DataSourceRequest model binding endpoint, potentially causing parsing errors or a StackOverflowException. The issue is fixed in version 2026.4.1111.