VulnerabilityPublished 11 Nov 2026

CVE-2026-124686: Progress Software Kendo UI for jQuery · Eval Injection

Affects Progress Software Kendo UI for jQuerySource CVE Database V5

Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2026.4.1111 when convenient.

Data as of 11 Nov 2026, 15:49 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (ProgressSoftware)	CVSS 3.1	5.4

Patch: Available – fixed in 2026.4.1111

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Progress Software Kendo UI for jQuery to 2026.4.1111.

Affected software

Product	Affected	Fixed in
Progress SoftwareKendo UI for jQuery	Affected >=2022.3.1109 <2026.4.1111	Fixed in 2026.4.1111

AI-suggested

Upgrade to Progress Kendo UI for jQuery version 2026.4.1111 or later, where this vulnerability is fixed. No other vendor advisory mitigation or workaround is provided.

Description

CVE-2026-124686 is an eval injection vulnerability in Progress Software's Kendo UI for jQuery. Versions from 2022.3.1109 up to but not including 2026.4.1111 are affected. The vulnerability arises because kendo.init() compiles data-* attribute values using new Function when invalid JSON is supplied, allowing low-privilege attackers to inject JavaScript that executes during widget initialization. Exploitation can compromise confidentiality and integrity of data in the user's browser context. The issue is fixed in version 2026.4.1111.

Impact

Successful exploitation allows an attacker with low privileges to inject and execute arbitrary JavaScript in the user's browser during widget initialization. This can lead to compromise of confidentiality and integrity of data accessible in the browser context. The CVSS v3.1 score is 5.4 (medium severity), reflecting network attack vector, low attack complexity, low privileges required, user interaction required, and impact on confidentiality and integrity but not availability.

CWE-95Improper Neutralization of Directives in Dynamically Evaluated Code (Eval Injection) (opens in a new tab)
Variant weaknessLikelihood of exploit: MediumOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval").
Architecture and Design · Implementation · Refactoring
If possible, refactor your code so that it does not need to use eval() at all.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180, CWE-181). Make sure that your application does not inadvertently decode the same input twice (CWE-174).
OWASP Cheat Sheets
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
OWASP ASVS 4.0.3
V5.5.4 (opens in a new tab)
V5.2.4 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Leverage Executable Code in Non-Executable Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

telerik.com/kendo-jquery-ui/documentation/knowledge-base/kb-security-kendo-init-code-injection-cve-2026-124686 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 15:49 UTC

WeaknessesCWE-95

Technical details

References

Community reviews

Related threats