# Telerik filter parsing: separate MVC and ASP.NET Core failure paths

Canonical: https://www.oktsec.com/radar/telerik-filter-processing-november-2026
Publisher: Oktsec
Language: en
Published: 2026-11-17T13:34:30Z
Updated: 2026-11-17T13:34:30Z
Record reviewed: 2026-11-17T13:34:30Z
Latest evidence check: 2026-11-17T13:34:30Z
Disclosed: 2026-11-13

Crafted filters sent to affected Telerik endpoints can cause request failures in ASP.NET MVC or uncontrolled recursion in ASP.NET Core. Both corrections are included in 2026.4.1111; the reachable endpoint and model binding determine exposure.

## Evidence and response priority

- Category: Vulnerability
- Oktsec priority: Review this week
- Rationale: The vendor provides a correction for both products. Exposure depends on filter processing; the reviewed notices establish neither remote code execution nor attacks.
- Evidence: Attacks not established
- Verification: Vendor confirmed
- Fix status: Fix available
- Exposure requirement: Application or configuration dependent
- Vendor: Progress
- Products: Telerik UI for ASP.NET MVC, Telerik UI for ASP.NET Core
- CVEs: CVE-2026-106146, CVE-2026-106154

## Technical overview

The MVC notice describes an uncaught FilterParserException resulting in HTTP 500. The reported behavior does not establish that the worker process terminates or that unrelated requests fail.

The ASP.NET Core issue follows a different path: insufficient limits on nested filter parsing can produce parsing errors or a StackOverflowException. An application must expose a route that passes the supplied filter through the affected model binding.

Neither notice establishes remote code execution or exploitation in production. The knowledge base pages were updated on November 13; finding them later does not date an attack. The correction must reach the deployed server component, with matching client assets.

## Recommended response

Update the affected Telerik server package to 2026.4.1111 or later, align client assets with that version and redeploy. Test filter endpoints and review parsing failures.

Relevant to: Developers and operators of applications using Telerik server components for ASP.NET.

## CVE attribution

- CVE-2026-106146: Progress — Telerik UI for ASP.NET MVC. [Source](https://www.telerik.com/aspnet-mvc/documentation/knowledge-base/kb-security-filter-processing-cve-2026-106146)
- CVE-2026-106154: Progress — Telerik UI for ASP.NET Core. [Source](https://www.telerik.com/aspnet-core-ui/documentation/knowledge-base/kb-security-uncontrolled-recursion-cve-2026-106154)

## Affected systems and fixes

### Telerik UI for ASP.NET MVC

Affected: 2012.2.710 through 2026.3.1015. Crafted filter parameters reach affected parsing code; anonymous access is possible where the application exposes that endpoint.

Fixed release / action: 2026.4.1111

### Telerik UI for ASP.NET Core

Affected: 2015.1.318 through 2026.3.1015. An accessible endpoint uses DataSourceRequest model binding; deeply nested filters can trigger uncontrolled recursion.

Fixed release / action: 2026.4.1111

Confirm the running version against the vendor advisory, including any distribution backports.

## CISA KEV evidence

Catalog: 2026.11.17
Checked: 2026-11-17T19:15:14.934Z

No matching CVE appears in the reviewed catalog snapshot.

CISA KEV inclusion establishes known exploitation of the listed CVE, not compromise of your environment. Absence does not rule out exploitation. The date added is not the first attack date. Federal deadlines and forensic triage requirements are context, not universal obligations for private organizations or businesses in Latin America.

## Supporting evidence

Snapshot checked: 2026-11-17T19:15:16.057Z. These dates do not change the incident’s editorial review date.

### FIRST EPSS forecast

- [CVE-2026-106154](https://api.first.org/data/v1/epss?cve=CVE-2026-106154): 0.37% probability of observed exploitation in the next 30 days; percentile 31.23%; score date 2026-11-17.
- [CVE-2026-106146](https://api.first.org/data/v1/epss?cve=CVE-2026-106146): 0.38% probability of observed exploitation in the next 30 days; percentile 32.16%; score date 2026-11-17.

EPSS is a prediction, not exploitation evidence or organization-specific risk. Confirmed exploitation takes precedence. A missing score is not zero. Check status: available; last successful check: 2026-11-17T19:15:16.057Z.

### Official regional advisories

- [Vulnerabilidades en Progress Telerik UI](https://www.cert.gov.py/vulnerabilidades-en-progress-telerik-ui/) — CERT-PY, Paraguay; publication 2026-11-17T10:54:20.000Z; observed 2026-11-17T19:15:16.057Z; matched by exact CVE identifier.

Publisher country does not establish victim location. Original notices may repeat the same underlying advisory.

## Response checklist

1. **Find the affected server components** — Check package versions and endpoints that accept Telerik filter descriptors. Assess anonymous access and DataSourceRequest binding separately for each application.
2. **Update packages and matching assets** — Install 2026.4.1111 or later using the product upgrade instructions. Align the server assemblies or NuGet package and the JavaScript and CSS assets; replacing browser files alone does not update the server parser.
3. **Test the deployed application** — Oktsec recommends exercising normal filtering after deployment and reviewing HTTP 500 responses, parser errors and process restarts. Confirm the version loaded by the application.

## Relevance to AI environments

Inventory deployed server dependencies, including internal applications used by automation.

## Sources

- [MVC CVE-2026-106146: filter parsing exception](https://www.telerik.com/aspnet-mvc/documentation/knowledge-base/kb-security-filter-processing-cve-2026-106146) — Progress Telerik; Vendor notice; checked 2026-11-17T13:34:30Z
- [Core CVE-2026-106154: uncontrolled recursion](https://www.telerik.com/aspnet-core-ui/documentation/knowledge-base/kb-security-uncontrolled-recursion-cve-2026-106154) — Progress Telerik; Vendor notice; checked 2026-11-17T13:34:30Z
- [MVC upgrade instructions](https://www.telerik.com/aspnet-mvc/documentation/installation/upgrading/upgrade) — Progress Telerik; Vendor notice; checked 2026-11-17T13:34:30Z
- [ASP.NET Core upgrade instructions](https://www.telerik.com/aspnet-core-ui/documentation/installation/upgrading/upgrade) — Progress Telerik; Vendor notice; checked 2026-11-17T13:34:30Z

## Editorial record

- 2026-11-17T13:34:30Z: Added verified scope, branch corrections and installation guidance from primary sources.

## Use this advisory in Radar

Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment.

[Open advisory](https://www.oktsec.com/radar/telerik-filter-processing-november-2026) · [Build a response plan](https://www.oktsec.com/radar/telerik-filter-processing-november-2026#review-workspace)

- [Exposure check consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=telerik-filter-processing-november-2026&service=exposure_check)
- [Patch verification consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=telerik-filter-processing-november-2026&service=patch_verification)

## Scope and corrections

Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure.

[Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.

