CVE
Progress Telerik UI for ASP.NET MVC uncaught exceptions in filter processing
Only affects Telerik UI for ASP.NET MVC 2012.2.710 through 2026.3.1015 on applications exposing an unauthenticated endpoint that accepts crafted filter parameters. Fixed in 2026.4.1111.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.4.1111
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2026.4.1111.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.38% · 32nd percentile
- 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? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- 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
Summary
Progress Software's Telerik UI for ASP.NET MVC mishandles crafted filter parameters during server-side processing, causing uncaught exceptions that return HTTP 500 errors. A remote attacker without logging in can trigger this on an application that exposes an unauthenticated endpoint accepting such filters, though the report does not show worker-process termination or disruption of other requests.
Read the original description
In Progress® Telerik® UI for ASP.NET MVC versions 2012.2.710 through 2026.3.1015, server-side filter processing does not properly validate descriptor types, null values, or stack state in FilterNodeVisitor and does not catch FilterParserException within the affected assembly. An unauthenticated remote attacker can exploit this if the application exposes an endpoint reachable without authentication that accepts crafted filter parameters. Affected requests can trigger uncaught cast, null-reference, or empty-stack exceptions and return HTTP 500. The report does not demonstrate worker-process termination or disruption of unrelated requests. The issue is fixed in version 2026.4.1111.
Who should check
Teams running Progress Telerik UI for ASP.NET MVC from 2012.2.710 through 2026.3.1015, especially where an endpoint accepts filter parameters without authentication.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2026.4.1111.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-106146 (Uncaught Exceptions in Telerik UI for ASP.NET MVC Filter Processing), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-106146 (entry last updated 2026-11-12):
Affected:
- Progress Software Telerik UI for ASP.NET MVC: from 2012.2.710, through 2026.3.1015
Fixed versions: 2026.4.1111.
Conditions (all must be true for the bug to be hit):
- Telerik UI for ASP.NET MVC versions 2012.2.710 through 2026.3.1015 (source: https://www.telerik.com/aspnet-mvc/documentation/knowledge-base/kb-security-filter-processing-cve-2026-106146)
- The application exposes an endpoint reachable without authentication that accepts crafted filter parameters (source: https://www.telerik.com/aspnet-mvc/documentation/knowledge-base/kb-security-filter-processing-cve-2026-106146)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-106146 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-106146 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.telerik.com/aspnet-mvc/documentation/knowledge-base/kb-security-filter-processing-cve-2026-106146
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-106146
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-106146"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Progress Software Telerik UI for ASP.NET MVC
From 2012.2.710 · through 2026.3.1015
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-106146
Is CVE-2026-106146 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
What does this mean?
Crafted filter requests can make the component throw uncaught cast, null-reference, or empty-stack exceptions, which return HTTP 500 errors for the affected requests. The advisory does not demonstrate that the worker process terminates.Source: telerik.com
Which versions are affected by CVE-2026-106146?
Telerik UI for ASP.NET MVC: from 2012.2.710 through 2026.3.1015.Source: cve.now feed data
Am I affected, and how do I check?
Versions 2012.2.710 through 2026.3.1015 of Telerik UI for ASP.NET MVC are affected, but only in applications that expose an endpoint reachable without authentication that accepts crafted filter parameters. To check, look at the Telerik UI for ASP.NET MVC version in the project's package references and review which filter-accepting endpoints are reachable without login.Source: telerik.com
How do I fix CVE-2026-106146?
Upgrade Telerik UI for ASP.NET MVC to version 2026.4.1111, which contains the fix.Source: telerik.com