Quick answers
- Is CVE-2026-106160 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106160 being exploited in the wild.
- How severe is CVE-2026-106160?
- Medium severity, with a CVSS score of 5.4, published 15 October 2026.
- Which products and versions are affected?
- Progress Kendo UI for jQuery prior to 2026.3.1015.
- Is there a fix for CVE-2026-106160?
- Yes: fixed in 2026.3.1015. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106160 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-106160?
- Check whether you run Progress Kendo UI for jQuery at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2026.3.1015
Technical details
The vulnerability is a prototype pollution flaw in Model.accept and kendo.setter that fail to sanitize server-response keys, allowing unsafe paths like __proto__, constructor, and prototype to be passed through. An authenticated attacker or one providing untrusted model data can modify object prototypes to influence downstream application behavior, including in server-side JavaScript contexts where the impact may be severe. The fix is available in version 2026.3.1015.
Affected products
- Progress Kendo UI for jQuery prior to 2026.3.1015
Timeline
- 2026-10-15: disclosed
- other: Earliest affected version not confirmed; versions prior to 2026.3.811 confirmed vulnerable