<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cve-2026-6022 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-6022/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 22 Apr 2026 08:16:12 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-6022/feed.xml" rel="self" type="application/rss+xml"/><item><title>Telerik UI for AJAX RadAsyncUpload Uncontrolled Resource Consumption (CVE-2026-6022)</title><link>https://feed.craftedsignal.io/briefs/2026-04-telerik-resource-exhaustion/</link><pubDate>Wed, 22 Apr 2026 08:16:12 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-telerik-resource-exhaustion/</guid><description>A vulnerability exists in Progress Telerik UI for AJAX prior to 2026.1.421, RadAsyncUpload, due to missing cumulative size enforcement during chunk reassembly, which allows file uploads to exceed the configured maximum size, leading to disk space exhaustion.</description><content:encoded><![CDATA[<p>Progress Telerik UI for AJAX, a suite of UI components for ASP.NET AJAX, contains an uncontrolled resource consumption vulnerability within the RadAsyncUpload component. This vulnerability, identified as CVE-2026-6022, affects versions prior to 2026.1.421. The vulnerability stems from a failure to properly enforce maximum file size limits during the reassembly of file chunks uploaded via the RadAsyncUpload component. An unauthenticated attacker could exploit this vulnerability by uploading a large file in chunks, bypassing the configured maximum file size restriction. Successful exploitation leads to excessive disk space consumption on the server, potentially causing denial of service.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker identifies a web application using a vulnerable version of Progress Telerik UI for AJAX with the RadAsyncUpload component enabled.</li>
<li>The attacker crafts an HTTP request to initiate a file upload to the RadAsyncUpload endpoint.</li>
<li>The attacker splits the malicious file into multiple chunks, each smaller than the initially configured maximum upload size limit.</li>
<li>The attacker sends each chunk to the server using separate HTTP requests to the RadAsyncUpload endpoint.</li>
<li>The server receives the chunks and stores them temporarily, without enforcing the cumulative file size.</li>
<li>Once all chunks are uploaded, the RadAsyncUpload component reassembles the file.</li>
<li>Due to the missing cumulative size check, the reassembled file exceeds the maximum allowed file size.</li>
<li>The server stores the complete, oversized file, leading to disk space exhaustion.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability can lead to a denial-of-service condition due to disk space exhaustion. The number of affected systems depends on the usage of the vulnerable Telerik UI for AJAX RadAsyncUpload component. Organizations in any sector using the affected Telerik component are potentially vulnerable. If successful, the attack can cause application downtime, data loss, and require administrative intervention to restore service.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Progress Telerik UI for AJAX to version 2026.1.421 or later to patch CVE-2026-6022.</li>
<li>Implement server-side monitoring for excessive disk space usage in directories associated with RadAsyncUpload temporary file storage.</li>
<li>Deploy the Sigma rule <code>DetectSuspiciousRadAsyncUploadChunks</code> to detect potential exploitation attempts.</li>
<li>Review and harden file upload size limits to prevent resource exhaustion, as described in the Telerik documentation referenced.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve-2026-6022</category><category>telerik</category><category>resource-exhaustion</category></item></channel></rss>