Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-106163 Overview
CVE-2026-106163 is a stored Cross-Site Scripting (XSS) vulnerability in Progress Kendo UI for jQuery. The flaw affects the FileBrowser and ImageBrowser components, which render remotely supplied file and directory names as HTML without proper encoding. An attacker who controls file or directory names on the server can inject script-related HTML that executes in the browser of any user who opens the component. The issue is tracked as CWE-80 (Improper Neutralization of Script-Related HTML Tags). It affects versions from v2023.1.117 up to, but not including, v2026.3.1015.
Critical Impact
Attacker-controlled filenames execute JavaScript in the context of the affected application, exposing session data, tokens, and user actions to theft or manipulation.
Affected Products
- Progress Kendo UI for jQuery v2023.1.117 through v2026.3.1014
- Applications embedding the Kendo FileBrowser component
- Applications embedding the Kendo ImageBrowser component
Discovery Timeline
- 2026-10-15 - CVE-2026-106163 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-106163
Vulnerability Analysis
The FileBrowser and ImageBrowser widgets in Kendo UI for jQuery display server-side file listings inside a client-side dialog. When the widgets render each entry, they insert the file or directory name into the Document Object Model (DOM) as HTML rather than as text. Any script-related tags or event handler attributes present in the name are parsed and executed by the browser.
The payload runs in the origin of the hosting application. That gives the attacker access to session cookies, authentication tokens stored in script-reachable storage, and any application state exposed through the DOM. The attacker can also issue authenticated requests on behalf of the victim.
Exploitation requires that the attacker influence filenames returned by the file provider. Common pathways include upload endpoints that preserve attacker-chosen names, shared network paths, or synchronized storage where users or external systems can create files.
Root Cause
The root cause is missing output encoding in the client-side rendering logic of the two browser components. File and directory names arriving from the server endpoint are concatenated into HTML templates instead of being escaped or inserted via text nodes. This is a classic [CWE-80] pattern where HTML special characters in untrusted input are not neutralized before DOM insertion.
Attack Vector
The vulnerability is network-reachable and requires no privileges or user interaction beyond opening the file browser dialog. An attacker uploads or stages a file whose name contains an HTML payload, for example a <script> tag or an onerror handler on an <img> element. When any user loads the Kendo FileBrowser or ImageBrowser pointing at that directory, the browser parses the payload and executes the attacker's JavaScript.
No verified public exploit code is available for CVE-2026-106163. Refer to the Telerik Security Advisory CVE-2026-106163 for vendor technical details.
Detection Methods for CVE-2026-106163
Indicators of Compromise
- Files or directories on application-managed storage whose names contain <, >, script, onerror, onload, or encoded equivalents.
- Server logs showing upload requests with filenames containing HTML tags or JavaScript event handlers.
- Outbound browser requests to unknown domains originating from pages that host the FileBrowser or ImageBrowser widgets.
Detection Strategies
- Inventory web applications and identify any that load kendo.all.min.js, kendo.filebrowser, or kendo.imagebrowser modules at versions between v2023.1.117 and v2026.3.1014.
- Enable Content Security Policy (CSP) reporting and monitor script-src violations originating from pages that render file listings.
- Review file provider endpoints that back the Kendo browsers and alert on filenames failing a strict allowlist of printable, non-markup characters.
Monitoring Recommendations
- Monitor web server access logs for GET requests to the Kendo file browser read action followed by anomalous outbound JavaScript-initiated traffic.
- Alert on new files whose names include angle brackets, backticks, or percent-encoded HTML sequences.
- Track administrator sessions that interact with the file browser, since compromise of a privileged session amplifies impact.
How to Mitigate CVE-2026-106163
Immediate Actions Required
- Upgrade Progress Kendo UI for jQuery to v2026.3.1015 or later across every application that embeds the FileBrowser or ImageBrowser widgets.
- Restrict upload endpoints and file provider back-ends to reject filenames containing HTML metacharacters.
- Rotate session tokens and credentials for any accounts that interacted with a file browser containing untrusted content.
Patch Information
Progress fixed the issue in Kendo UI for jQuery v2026.3.1015. The patched release encodes file and directory names before DOM insertion in both affected components. Full details are available in the Telerik Security Advisory CVE-2026-106163.
Workarounds
- Sanitize filenames server-side before they are returned by the Kendo file provider, stripping or rejecting <, >, ", ', and &.
- Deploy a strict Content Security Policy that disallows inline scripts and restricts script-src to trusted origins.
- Temporarily disable the FileBrowser and ImageBrowser features in editors such as the Kendo Editor until the upgrade is deployed.
# Example server-side filename allowlist (pseudocode)
# Reject uploads whose names contain HTML metacharacters
if filename matches /[<>"'&]/:
reject upload with HTTP 400
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

