Medium

CVE-2026-106149 — Cross-site Scripting (XSS) in Kendo UI for jQuery Menu

In Progress® Kendo® UI for jQuery prior to v2026.3.1015, the Menu component constructs HTML attributes from bound dataSource fields by string concatenation without proper neutralization. An attacker with low privileges who can control these fields can inject JavaScript event-handler attributes that execute when a user interacts with the affected Menu, compromising the confidentiality and integrity of data accessible in the user's browser context.

Published Oct 15, 2026 · Updated Oct 15, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · CNA: ProgressSoftware

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Progress Software

Kendo UI for jQuery

CVSS base

5.4

Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Progress Software Kendo UI for jQuery).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Progress Software	Kendo UI for jQuery	≥ 2011.2.804 and < 2026.3.1015	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.4	CVSS 3.1	Medium	2.3	2.7	security@progress.com via NIST National Vulnerability Database
5.4	CVSS 3.1	Medium	—	—	ProgressSoftware via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (score shown at the top: security@progress.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-80

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Source status changed · Received → Awaiting Analysis
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · Published → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record published
Oct 15, 2026
Affected products added · progress software/kendo ui for jquery
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
CVSS changed · 5.4
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Published
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record created in this database
Oct 15, 2026 · Alertas do Telegram
CVE published
Oct 15, 2026 · ProgressSoftware

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 15, 2026 – Oct 15, 2026
1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

www.telerik.com/kendo-jquery-ui/documentation/knowledge-base/kb-security-menu-xss-cve
vendor-advisory, CVE Program (cve.org) e CISA ADP

Elsewhere on this site

Progress Software
every CVE for this vendor

CWE-80
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-106150 Cross-site Scripting (XSS) in Kendo UI for jQuery Splitter, Window, and Tooltip 2h
Medium CVE-2026-106151 Cross-Site Scripting in Validator Validation Messages in Kendo UI for jQuery 2h
Medium CVE-2026-106153 Cross-site Scripting (XSS) in Kendo UI for jQuery Calendar and MultiViewCalendar 2h
High CVE-2026-108116 MDX and SOAP Injection in Kendo UI for jQuery 2h
Medium CVE-2026-106163 Cross-site Scripting (XSS) in Kendo UI for jQuery FileBrowser and ImageBrowser 3h
Medium CVE-2026-106147 Cross-Site Scripting via ListBox Bound Text in Kendo UI for jQuery 3h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-106149 is "Cross-site Scripting (XSS) in Kendo UI for jQuery Menu", rated Medium. It affects Kendo UI for jQuery (Progress Software); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.4 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.