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-106161 Overview
CVE-2026-106161 is a stored cross-site scripting (XSS) vulnerability in Progress Kendo UI for jQuery. The Badge widget's text method renders string values as raw HTML without encoding, including values supplied through text binding. Attackers who can influence data bound to a Badge can inject HTML containing event handlers that execute JavaScript in a victim's browser. The flaw is tracked under CWE-80: Improper Neutralization of Script-Related HTML Tags. It affects releases from v2020.1.114 through versions prior to 2026.3.1015.
Critical Impact
Successful exploitation compromises the confidentiality and integrity of data accessible to the affected web application, including session context and rendered user data.
Affected Products
- Progress Kendo UI for jQuery v2020.1.114 and later
- Progress Kendo UI for jQuery releases prior to 2026.3.1015
- Applications using the Badge widget with text binding to attacker-influenced data
Discovery Timeline
- 2026-10-15 - CVE-2026-106161 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-106161
Vulnerability Analysis
The vulnerability resides in the Badge widget's text method within Progress Kendo UI for jQuery. The method writes supplied string values directly into the DOM without HTML entity encoding. Any binding path that updates the Badge text, including declarative text binding in MVVM scenarios, inherits the same unsafe rendering behavior.
Because the Badge is commonly used to display dynamic counts, labels, or status indicators tied to backend data, user-controlled fields can reach the widget through legitimate application flows. An attacker who can modify the bound source, for example via a prior write to a shared resource, can plant HTML markup containing event handlers such as onerror or onmouseover. The payload executes when another user's browser renders the Badge.
Exploitation requires low privileges and user interaction, and the attack crosses a security scope boundary when the injected script runs in the context of the hosting application. Impact is bounded to the privileges of the targeted user session but typically includes session token theft, data exfiltration, and unauthorized actions performed as the victim.
Root Cause
The Badge text method treats input as trusted HTML rather than text content. Values are inserted using an HTML-rendering path instead of textContent or an encoded equivalent, allowing arbitrary tags and inline event handlers to be parsed and executed.
Attack Vector
An authenticated attacker writes a payload containing an HTML element with an event handler into a data source bound to a Badge widget. When a victim loads a view that renders the Badge, the browser parses the injected markup and fires the event handler, executing attacker-controlled JavaScript under the application's origin. See the Telerik Security Advisory CVE-2026-106161 for vendor-provided details.
Detection Methods for CVE-2026-106161
Indicators of Compromise
- Stored records bound to Badge widgets containing HTML tags, inline event handlers such as onerror, onload, or onmouseover, or javascript: URIs.
- Content Security Policy (CSP) violation reports originating from pages that render Badge widgets.
- Unexpected outbound requests from authenticated user sessions shortly after rendering pages that include Kendo Badges.
Detection Strategies
- Inventory applications using Progress Kendo UI for jQuery and identify versions between v2020.1.114 and 2026.3.1015 using software composition analysis.
- Search source code for calls to the Kendo Badge text method and data-bind="text:" expressions targeting Badge instances.
- Scan datastores backing Badge-bound fields for stored HTML markup or script-like substrings.
Monitoring Recommendations
- Enable and review CSP report-only or enforced policies to surface inline script execution on pages that render Kendo widgets.
- Log and alert on administrative or user writes to fields known to feed Badge widgets, especially payloads containing < or on\w+= patterns.
- Monitor browser error telemetry and web application firewall (WAF) logs for XSS signatures targeting Kendo UI endpoints.
How to Mitigate CVE-2026-106161
Immediate Actions Required
- Upgrade Progress Kendo UI for jQuery to version 2026.3.1015 or later across all affected applications.
- Audit stored data bound to Badge widgets and remove any records containing HTML markup or event handler attributes.
- Rotate session tokens for users who may have viewed pages rendering untrusted Badge content prior to patching.
Patch Information
The issue is fixed in Progress Kendo UI for jQuery 2026.3.1015. Refer to the Telerik Security Advisory CVE-2026-106161 for the official fix and upgrade guidance.
Workarounds
- Encode or strip HTML from values before assigning them to the Badge text method or binding target, using a server-side sanitizer or a DOM-safe helper on the client.
- Deploy a strict Content Security Policy that disallows inline event handlers and inline scripts to reduce impact of residual XSS sinks.
- Restrict write access to data sources that feed Badge widgets so that only trusted roles can modify bound fields.
# Configuration example
# Example strict CSP header to limit inline script execution
Content-Security-Policy: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'
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

