Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft corrupted XLS file
-
ExploitSubmit file to import endpoint
-
ExecutionParser enters infinite loop ignoring timeout
-
ImpactCPU thread pinned, service denial
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Loop termination conditions
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an application built on the Telerik SpreadProcessing library (versions prior to 2026.3.1006) to import an attacker-supplied XLS file containing a specifically-targeted corruption; the crafted structure causes the import routine to loop indefinitely and bypass the library's configured import timeout, so the timeout safeguard provides no protection. Exploitation is limited by whether the host application actually exposes an XLS import path to untrusted input - purely internal/trusted import workflows are not realistically reachable by external attackers. The flaw affects the XLS import format specifically (not inherently other formats) and is remediated by upgrading to 2026.3.1006 or later. |
| Impact | This is a denial-of-service vulnerability (CWE-835, infinite loop) in the Telerik SpreadProcessing library, triggered when a specially-corrupted XLS file is imported and the import timeout is ignored. The vendor-supplied CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L, score 7.3) is internally inconsistent with the described impact: a DoS caused by an unresponsive CPU thread should present as availability-only (A:H, C:N, I:N), yet the vector claims low confidentiality and integrity impact with only low availability impact - this is a data-quality concern and the real-world impact is availability, not data disclosure or tampering. No EPSS score, no CISA KEV listing, and no public exploit were provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Practical risk is moderate and context-dependent: because this is a developer library rather than a standalone service, exploitability hinges entirely on whether a downstream application built on SpreadProcessing accepts and imports attacker-controlled XLS files. Where such an upload/import path exists, a single crafted file can pin a worker thread indefinitely; where imports are limited to trusted internal files, real risk is low. The AV:N rating reflects the library's use in server-side import pipelines rather than any inherent network listener. |
| Exploit ScenarioDerived | An attacker uploads a maliciously-corrupted XLS file to a web application or service that uses Telerik SpreadProcessing to parse spreadsheets. When the application imports the file, the parser enters an infinite loop and ignores its configured import timeout, pinning a CPU thread and degrading or denying service to legitimate users. No public exploit code was identified at time of analysis, though the corruption technique is deterministic and would be straightforward to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Denial of service in Progress Telerik Document Processing's SpreadProcessing library (all versions prior to 2026.3.1006) allows unauthenticated remote attackers to hang an application CPU thread indefinitely by supplying a specifically corrupted XLS spreadsheet for import. The crafted file drives the XLS import routine into an infinite loop that ignores the library's configured import timeout, so the built-in timeout safeguard offers no protection and the affected worker thread becomes permanently unresponsive. Practical exposure depends on whether the host application actually accepts XLS uploads or imports from untrusted sources; no public exploit code or confirmed active exploitation has been identified at time of analysis, and impact is availability-only per our assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), with the vendor publishing a base score of 7.3.
RemediationAI
Apply the vendor fix by upgrading the Telerik Document Processing Libraries to version 2026.3.1006 or later, which is the exact release that addresses CVE-2026-106164 (see the Telerik knowledge-base advisory at https://www.telerik.com/document-processing-libraries/documentation/knowledge-base/kb-security-import-infinite-loop-cve-2026-106164); because the library ships as NuGet packages referenced by consuming applications, every dependent service must be rebuilt and redeployed, and any shaded/vendored copies must be updated separately. Where immediate upgrade is impossible, treat the library's own import timeout as ineffective and enforce controls outside the library: run XLS parsing in a dedicated, sandboxed worker process that can be hard-killed by an external watchdog with a short wall-clock limit (trade-off: added process-management complexity and possible loss of partially parsed documents), cap CPU quota and thread-count per import so a stuck loop degrades at most one constrained worker (trade-off: throttles legitimate large-file conversions), and restrict or disable XLS upload/import from untrusted sources entirely, accepting only XLSX or pre-converted files (trade-off: breaks legitimate legacy-format workflows and can be bypassed if an alternate import path still accepts XLS). File-size limits, MIME/extension allowlists, and generic antivirus scanning should be considered weak controls here, since the trigger is a specifically crafted structural corruption likely to pass signature-based and size-based filters. Monitor document-processing workers for runaway CPU threads as a detection signal for attempted exploitation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is an uncontrolled resource-consumption / infinite loop (CWE-835) in the XLS import path of the Progress Telerik Document Processing Libraries, tracked under the wildcard CPE cpe:2.3:a:progress_software:telerik_document_processing_libraries:*:*:*:*:*:*:*:* which does not enumerate discrete versions and must be read as 'all releases of the library before the fixed build'. SpreadProcessing is a document-model library used by .NET applications (ASP.NET, Blazor, WPF, WinForms, and server-side services) to read, convert, and generate spreadsheet content without requiring Microsoft Excel or Office interop; the XLS reader is a legacy BIFF-format parser, and a precisely targeted corruption in the file structure causes the parsing loop's termination condition never to be reached. The key technical detail is that the import timeout mechanism implemented by the library is not evaluated on the looping code path, so the intended self-protection for long-running parses is bypassed rather than merely exceeded. Because the loop burns CPU on a single thread, an attacker who can repeatedly submit such files can pin one or more worker threads, degrading or halting request processing in the consuming application; the library itself performs no authentication, so reachability is a function of the embedding application's import surface. Remediation is by upgrading to 2026.3.1006 or later, per the Telerik knowledge-base advisory for CVE-2026-106164.
Know when Telerik Document Processing Libraries gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Infinite loop ignoring timeout causes thread/service exhaustion, so A:H with no confidentiality or integrity impact; attacker-supplied file reaches server-side import pipeline giving AV:N/PR:N.
Primary rating from Vendor (ProgressSoftware).
CVSS VectorVendor: ProgressSoftware
Lifecycle Timeline
2DescriptionCVE.org
In Progress® Telerik® Document Processing SpreadProcessing library, versions prior to 2026.3.1006, an infinite loop vulnerability exists when importing an XLS file with a specifically-targted corruption, the import timeout is ignored resulting in an unresponsive CPU thread and denial of service.
Executive ViewAI
Progress Telerik Document Processing's SpreadProcessing library - a component embedded in many internal and customer-facing .NET applications that handle spreadsheets - can be driven into a permanent CPU thread hang by a deliberately corrupted XLS file, and the library's own import timeout does not stop it. No credentials or user interaction are required, so any service that accepts spreadsheet uploads from end users, partners, or untrusted sources can lose worker threads until processing capacity is exhausted and the application becomes unavailable to all of its users. Leadership should treat this as an availability and resilience exposure affecting the host applications built on this library rather than the library in isolation, particularly where no vendor fix is currently available.
No vendor-released patch identified at time of analysis. Interim mitigations: disable or allow-list XLS import paths where they are not business-critical; convert or reject legacy .XLS (BIFF) files at the perimeter; parse documents in an isolated, resource-capped worker process with a hard kill timeout enforced externally; rate-limit and cap concurrent imports per source; apply WAF/content-inspection rules for malformed XLS binaries; and monitor thread-pool and CPU saturation for hung workers.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
In Progress® Telerik® Document Processing Libraries, versions prior to 2025 Q1 (2025.1.205), unzipping an archive can le
A crafted XLSX or XLS workbook, or a crafted formula inside one, can terminate or hang the host process that parses it w
Denial of service in Progress Telerik Document Processing Libraries before 2026.3.1027 allows unauthenticated remote att
Denial of service in Progress Telerik Document Processing Libraries before 2026.3.1027 allows an unauthenticated remote
RadPdfProcessing, the PDF component of Progress Telerik Document Processing Libraries before version 2026.3.1027, perfor
XML external entity injection in Progress Telerik Document Processing Libraries before 2026.3.1027 allows remote unauthe
In Progress® Telerik® Document Processing Libraries, versions prior to 2025 Q1 (2025.1.205), using .NET Standard 2.0, th
Path traversal in Progress Telerik Document Processing Libraries before 2026.3.1027 allows an authenticated, low-privile
In Progress Telerik Document Processing Libraries, versions prior to 2024 Q4 (2024.4.1106), importing a document with un
EUVD-2026-94545
GHSA-3g99-jr36-v2mm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB