Skip to main content

Telerik SpreadProcessing EUVDEUVD-2026-94545

| CVE-2026-106164 HIGH
Loop with Unreachable Exit Condition (Infinite Loop) (CWE-835)
2026-10-07 ProgressSoftware GHSA-3g99-jr36-v2mm
7.3
CVSS 3.1 · Vendor: ProgressSoftware
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft corrupted XLS file
  2. Exploit
    Submit file to import endpoint
  3. Execution
    Parser enters infinite loop ignoring timeout
  4. Impact
    CPU 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Telerik Document Processing Libraries 2026.3.811 <2026.3.1006

Affected Packages

euvd telerik_document_processing_libraries fix: 2026.3.1006

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

Vendor (ProgressSoftware) PRIMARY 7.3 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
vuln.today AI 7.5 HIGH

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.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (ProgressSoftware).

CVSS VectorVendor: ProgressSoftware

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Lifecycle Timeline

2
Patch available
Oct 07, 2026 - 20:17 EUVD
CVE Published
Oct 07, 2026 - 18:02 cve.org
HIGH 7.3

DescriptionCVE.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

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Medium
popular commercial .NET document library, common in enterprise apps but not ubiquitous
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy