Is there a public exploit for CVE-2026-106137?

No public exploit for CVE-2026-106137 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-106137?

CVE-2026-106137 scores CVSS 8.6 (v3.1), rated high.

What does CVE-2026-106137 affect?

CVE-2026-106137 affects Progress Software Telerik UI for ASP.NET MVC.

8.6 High

In affected versions of Progress® Telerik® UI for ASP.NET MVC 2012.2.710 through 2026.3.811, ClassFactory updates a shared class dictionary…

CVE-2026-106137

In affected versions of Progress® Telerik® UI for ASP.NET MVC 2012.2.710 through 2026.3.811, ClassFactory updates a shared class dictionary without exclusive write protection and emits non-collectible dynamic assemblies that remain loaded for the AppDomain's lifetime. The dictionary lookup and insertion are not atomic, and case variations in aggregate descriptors can produce distinct retained types even though member resolution is case-insensitive. An unauthenticated remote attacker can exploit this if the application exposes an aggregation endpoint that is reachable without authentication, by submitting concurrent or repeated crafted requests. These requests may corrupt dictionary state or increase CPU and memory use, potentially degrading availability. The issue is fixed in version 2026.3.1015.

Assessment

CVSS: 8.6 (v3.1)
Severity: High
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 11 November 2026
Last updated: 11 November 2026
Affected: Progress Software · Telerik UI for ASP.NET MVC
Assigner: ProgressSoftware

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

At the source

EUVD (ENISA)

References

https://www.telerik.com/aspnet-mvc/documentation/knowledge-base/kb-security-class-factory-cve-2026-106137

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 9 + 7? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-106137