Quick answers
- Is CVE-2026-106156 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106156 being exploited in the wild.
- How severe is CVE-2026-106156?
- High severity, with a CVSS score of 8.6, published 11 November 2026.
- Which products and versions are affected?
- Progress Telerik UI for ASP.NET Core 2015.1.318 through 2026.3.811.
- Is there a fix for CVE-2026-106156?
- 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-106156 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106156?
- 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.3.1015
Technical details
The vulnerability is an uncontrolled resource consumption flaw in server-side aggregation request handling within Telerik UI for ASP.NET Core. Repeated aggregation requests with or without grouping cause dynamic assemblies and load contexts to persist in memory rather than being released, leading to unbounded memory growth. An unauthenticated remote attacker can trigger this via direct requests to aggregation endpoints, even if grouping is disabled in the UI.
Affected products
- Progress Telerik UI for ASP.NET Core 2015.1.318 through 2026.3.811
Timeline
- 2026-11-11: disclosed