CVE-2026-119102 in Telerik UI for Blazorinfo

Summary

by MITRE • 11/13/2026

In Telerik UI for Blazor, versions v12.0.0 through 15.2.0, an improper input validation vulnerability exists, where the Grid, TreeList and Gantt's AI command filters on any model property, bypassing the declared column allowlist.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/13/2026

The identified vulnerability in Telerik UI for Blazor versions v12.0.0 through 15.2.0 represents a critical failure in input validation mechanisms within server-side rendering components such as the Grid, TreeList, and Gantt controls. This flaw specifically affects the artificial intelligence command filters that allow users to apply dynamic filtering criteria based on model properties. The core technical issue stems from an improper enforcement of access control policies where the application fails to strictly validate user-supplied input against a predefined whitelist of allowed column names before processing filter requests. Instead of restricting operations exclusively to columns explicitly permitted by the developer configuration, the framework inadvertently accepts and processes property names that fall outside this declared allowlist. This behavior indicates a logic error in how the backend interprets client-side filtering parameters, allowing an attacker or malicious user to inject arbitrary property identifiers into the query execution pipeline.

From a technical perspective, this vulnerability aligns with CWE-20 Improper Input Validation and CWE-798 Use of Hard-coded Credentials if sensitive properties are exposed through data leakage. The absence of rigorous server-side validation allows for potential information disclosure vulnerabilities where an attacker can enumerate internal model structures by observing error responses or successful retrieval of restricted fields. In the context of the MITRE ATT&CK framework, this behavior is consistent with T1078 Valid Accounts if combined with authentication bypass techniques, but more directly relates to data exfiltration tactics such as T1530 Data from Information Repositories via unauthorized access patterns. The vulnerability enables an attacker to potentially read sensitive data fields that were not intended for public or user-facing consumption, thereby compromising the confidentiality of the application's underlying business logic and data model.

The operational impact of this flaw is significant depending on the sensitivity of the exposed properties. If the affected components handle personal identifiable information, financial records, or proprietary business metrics, unauthorized access to these fields via improper filter injection can lead to severe regulatory compliance violations under frameworks such as GDPR or HIPAA. Furthermore, the ability to bypass column allowlists undermines the principle of least privilege applied at the data presentation layer, potentially facilitating further attacks such as SQL injection if the underlying ORM does not properly parameterize queries derived from these dynamic filters. Attackers could leverage this weakness to construct complex query payloads that extract large volumes of restricted data in a single request or through iterative probing techniques.

Mitigation strategies must focus on enforcing strict server-side validation regardless of client-side constraints. Developers should ensure that all filter inputs are validated against an explicit allowlist of permitted property names before being passed to the underlying data access layer. Implementing robust input sanitization routines and utilizing parameterized queries will prevent arbitrary property resolution. Additionally, upgrading to a patched version of Telerik UI for Blazor where this validation logic has been corrected is the primary remediation path. Security teams should also audit existing implementations of Grid, TreeList, and Gantt components to verify that no custom extensions have reintroduced similar vulnerabilities by bypassing standard framework safeguards. Regular security testing including dynamic application security testing can help identify such input validation gaps in production environments before they are exploited for data exfiltration.

Responsible

ProgressSoftware

Reservation

10/29/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00364

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!