SumatraPDF
CVE-2026-107730
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious LIT file with overflowing header values
-
DeliveryDeliver file to victim via email or download
-
ExploitVictim opens file in SumatraPDF
-
ExecutionSigned 32-bit offset overflows to negative, invalid read in LitU32()
-
ImpactApplication terminates (denial of service)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to open an attacker-crafted LIT (Microsoft Reader / .lit eBook) file in SumatraPDF version 3.7.0.22298; the malicious file must contain header fields (hdrLen >= 0x28, nPieces between 5 and 16) specifically tuned so that the signed 32-bit expression hdrLen + nPieces * 16 overflows into a negative section offset reaching LitU32(). Limiting factors are significant: the CVSS vector is AV:L with UI:R, so the attack is not remote and not automatable - it depends entirely on local delivery and the user actively opening the crafted document. No authentication is needed (PR:N) and no non-default configuration is required beyond the application's standard LIT parsing path, but the LIT format is legacy and far less commonly handled than PDF, narrowing the realistic attack surface. |
| Impact | All available signals converge on this being a low-to-moderate priority, denial-of-service-only defect rather than a high-impact threat. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, base 5.5 MEDIUM) explicitly scopes impact to availability only, and the description corroborates this: an integer overflow in LitParseHeader() leads to an invalid read in LitU32() causing 'deterministic application termination' with no demonstrated code execution, information disclosure, arbitrary read, or integrity impact. No EPSS score was provided, the CVE is not on CISA KEV, and no public exploit was identified - so there is no public exploit identified at time of analysis. There are notable conflicts in the supplied metadata: the input Tags list 'RCE' and 'Information Disclosure', but the description directly and explicitly rules out both code execution and information disclosure, so those tags appear mislabeled and should not drive prioritization. The realistic risk is a crash of the reader process when a victim opens a malicious LIT file - annoying and reliable, but not a confidentiality or integrity threat. Note also that although the input states 'No fixed version is available,' a fix commit (10a83278) is already present in the vendor repository, so remediation code exists even if a tagged release does not. |
| Exploit ScenarioDerived | An attacker crafts a malicious LIT (Microsoft Reader eBook) file whose header fields (hdrLen and nPieces) are chosen so that the signed 32-bit computation hdrLen + nPieces * 16 overflows to a negative section offset. The victim is socially engineered into opening the file in SumatraPDF 3.7.0.22298, at which point pointer construction reaches an invalid read in LitU32() and the application deterministically crashes. No public exploit code was identified, though the vendor fix commit illustrates the exact overflow condition. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Opening a specially crafted Microsoft Reader (.lit) ebook in SumatraPDF 3.7.0.22298 terminates the application deterministically: an integer overflow in LitParseHeader() allows a tuned header to compute a negative section offset that is later dereferenced, producing an out-of-bounds read and a crash. Per the authoritative assessment, impact is denial of service only - the supplied evidence demonstrates no code execution, information disclosure, arbitrary read, or integrity impact, despite RCE and Information Disclosure tags appearing alongside this record. Exploitation is not remote or automatable: it requires local delivery of the malicious .lit file and the user actively opening it (CVSS AV:L/UI:R, PR:N), and no public exploit code has been identified at time of analysis; the issue is not listed in CISA KEV.
RemediationAI
No vendor-released fixed version is confirmed in the available data; the CVE description states no fixed version was available as of the review, while an upstream fix exists as commit 10a83278a5a6f67194dedfb67c47474d22ecfe4b in sumatrapdfreader/sumatrapdf (64-bit bounds checks in LitU16/LitU32 plus a secHdrLen < 0 rejection and an (i64)hdrLen + (i64)nPieces * 16 > len(d) bound in LitParseHeader), so the status is best described as: upstream fix available (PR/commit); released patched version not independently confirmed. Track GHSA-vfpj-qhvj-92wg and the SumatraPDF project release notes for a build that carries the commit, and upgrade as soon as a release containing it ships. Until then, the only reliable mitigation is behavioral, since there is no documented configuration flag to disable the LIT parser: treat all .lit files as untrusted, block or strip .lit attachments at mail and web gateways and quarantine them on file shares so users cannot casually double-click them, and educate users that .lit is a legacy Microsoft Reader format and an unexpected .lit file should not be opened in SumatraPDF. Because the failure is a deterministic crash rather than memory corruption with demonstrated exploitability, detecting and alerting on repeated SumatraPDF process terminations immediately after opening a document is a reasonable detection control; note that each of these measures reduces convenience for legitimate legacy ebook viewers but does not eliminate the crash if a user opens a hostile file directly. No generic 'defense in depth' substitution removes the flaw - the code fix is the only complete remedy.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The defect is an integer overflow (CWE-190) in the LIT (Microsoft Reader / .lit ebook) parser of SumatraPDF, specifically in LitParseHeader() in src/LitDoc.cpp. The function reads attacker-controlled 32-bit fields - a header length (hdrLen) and a section count (nPieces, constrained to 5-16) - and computes a file offset as hdrLen + nPieces * 16 using signed 32-bit arithmetic. Because the aggregate is never validated against the actual file length before being used, sufficiently large component values wrap the sum to a negative number. That negative value flows into pointer construction and reaches the LitU32() accessor, whose bounds check (off < 0 || off + 4 > len(d)) is itself performed in 32-bit int arithmetic, so the oversized offset can also wrap when the check is evaluated, yielding an invalid read rather than a clean rejection. The upstream fix hardens both layers: the accessors LitU16()/LitU32() now compute their comparisons in 64-bit (i64) arithmetic, and LitParseHeader() adds a secHdrLen < 0 rejection plus a 64-bit bound check, (i64)hdrLen + (i64)nPieces * 16 > len(d), so the offset can never silently overflow before use. CPE data (cpe:2.3:a:sumatrapdfreader:sumatrapdf:*:*:*:*:*:*:*:*) lists the whole product line as in scope, though the flaw is confirmed in 3.7.0.22298.
Know when Sumatrapdf 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:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Attacker needs the victim to open a malicious local file (AV:L, UI:R) with no privileges (PR:N); impact is a deterministic crash only, so C:N/I:N/A:H.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
DescriptionCVE.org
SumatraPDF is a multi-format reader for Windows. In 3.7.0.22298, LitParseHeader() in src/LitDoc.cpp computes the attacker-controlled hdrLen + nPieces * 16 section offset using signed 32-bit arithmetic without validating the complete result. When the component values make that aggregate calculation overflow to a negative value, pointer construction reaches an invalid read in LitU32(), causing deterministic application termination. The supplied evidence does not demonstrate code execution, information disclosure, arbitrary read, or integrity impact. No fixed version is available as of this review.
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
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
Affected Products (CPE)CVE.org
More in Sumatrapdf
View allSumatraPDF 3.5.2 and earlier on Windows contains an untrusted search path vulnerability in the Advanced Options feature
SumatraPDF 3.5.2 and earlier on Windows allows arbitrary code execution when a user opens a PDF and selects "Show in fol
SumatraPDF versions 3.5.0 through 3.5.2 fail to validate TLS certificates during software updates and execute installers
Heap-based buffer overflow in SumatraPDF before 2.1 allows remote attackers to execute arbitrary code via a crafted PDF
Heap-based buffer overflow in SumatraPDF before 2.1 allows remote attackers to execute arbitrary code via a crafted PDF
SumatraPDF versions 3.5.2 and earlier are vulnerable to a heap buffer over-read in the MOBI file parser due to incomplet
SumatraPDF on Windows is vulnerable to a denial-of-service attack through a maliciously crafted Mobi file that triggers
A buffer overflow in SumatraPDF Reader v3.4.6 allows attackers to cause a Denial of Service (DoS) via a crafted text fil
Local code execution in SumatraPDF 3.6.1 and earlier on Windows is possible when a user opens an attacker-supplied docum
Parsing a malformed PDF in SumatraPDF 3.6.1 can crash the reader through a signed integer overflow in the PageLabels han
Command-line argument injection in SumatraPDF 3.5.2 and earlier lets an attacker-controlled SyncTeX source filename esca
Argument injection in the AI translation feature of SumatraPDF 3.6.1 and earlier allows text placed in a document select
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB