Uncontrolled Recursion in Telerik UI for ASP.NET Core FilterParser
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Progress Software | Telerik UI for ASP.NET Core | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Progress | Telerik Ui For Asp.net Core |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Progress
Progress telerik Ui For Asp.net Core |
|
| Vendors & Products |
Progress
Progress telerik Ui For Asp.net Core |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Progress® Telerik® UI for ASP.NET Core versions `2015.1.318` through `2026.3.1015`, the server-side FilterParser processes nested expressions in untrusted filter parameters through recursive parsing without a recursion-depth limit, while FilterLexer does not enforce an input-length limit. An unauthenticated remote attacker can exploit this if the application exposes an endpoint using DataSourceRequest model binding that is reachable without authentication. Deeply nested filters can trigger parsing errors during model binding or cause `StackOverflowException`. This issue is fixed in version `2026.4.1111`. | |
| Title | Uncontrolled Recursion in Telerik UI for ASP.NET Core FilterParser | |
| Weaknesses | CWE-674 | |
| References |
| |
| Metrics |
cvssV3_1
|