Quick answers
- Is CVE-2026-106154 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106154 being exploited in the wild.
- How severe is CVE-2026-106154?
- High severity, with a CVSS score of 8.6, published 12 November 2026.
- Which products and versions are affected?
- Progress Telerik UI for ASP.NET Core 2015.1.318 through 2026.3.1015.
- Is there a fix for CVE-2026-106154?
- Yes: fixed in 2026.4.1111. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106154 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106154?
- Check whether you run Progress Telerik UI for ASP.NET Core 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.4.1111
Technical details
The FilterParser component processes nested filter expressions from untrusted DataSourceRequest model binding without enforcing recursion depth limits, while FilterLexer lacks input-length validation. An unauthenticated remote attacker can exploit this via deeply nested filter parameters sent to any endpoint using DataSourceRequest that lacks authentication, triggering StackOverflowException and denial of service. A fix is available in version 2026.4.1111.
Affected products
- Progress Telerik UI for ASP.NET Core 2015.1.318 through 2026.3.1015
Timeline
- 2026-11-12: disclosed