CVE-2026-124693
Cross-Site Scripting in Kendo UI for jQuery PivotGrid Axis Chips
In Progress Kendo UI for jQuery versions 2026.3.1015 up to, but not including, 2026.4.1110, PivotGrid and PivotConfigurator axis field names are passed to a chip template without appropriate encoding. An attacker who can influence an axis field name can cause JavaScript to execute when a user views the rendered chip. The field name can be interpreted as HTML in both attribute and element contexts. Successful exploitation may compromise the confidentiality and integrity of data available in the user's browser context. The first affected release has not been established.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Kendo UI for jQuery Progress Software |
≥ 2026.3.1015; < 2026.4.1110 (affected, custom) 2026.4.1110 (unaffected) Other versions: unknown |
CNA: ProgressSoftware |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 7.1 high |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L | CNA: ProgressSoftware |
| 3.1 / 7.1 high |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L | NVD: [email protected] |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://www.telerik.com/kendo-jquery-ui/documentation/knowledge-base/kb-security-kendo-pivotgrid-pivotconfigurator-axis-chip-xss-cve-2026-124693CNA: ProgressSoftware · vendor-advisory
- https://www.telerik.com/kendo-jquery-ui/documentation/knowledge-base/kb-security-kendo-pivotgrid-pivotconfigurator-axis-chip-xss-cve-2026-124693[email protected]
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.