Sumatrapdfreader
Monthly
Argument injection in the AI translation feature of SumatraPDF 3.6.1 and earlier allows text placed in a document selection or clipboard to be interpreted as command-line flags when an agentic CLI backend (Grok, Claude Code, or Codex) is configured as the translation provider. Because the vulnerable code builds the child process command line with quote-only escaping, attacker-controlled text can smuggle in flags that alter the model, working directory, approval mode, or sandbox settings used by the launched CLI. Exploitation is local and requires the user to actively invoke the translate/AI-chat action on the crafted text, and only affects installations where one of those agentic CLI backends is installed and selected; no public exploit code was identified at time of analysis, and the issue is not in CISA KEV.
Command-line argument injection in SumatraPDF 3.5.2 and earlier lets an attacker-controlled SyncTeX source filename escape the quoting of an external editor's command template and inject arbitrary flags when a victim triggers inverse search. The attack is strictly conditional: it requires a PDF paired with a crafted sibling .synctex.gz file, a configured or auto-detected inverse-search editor, and a deliberate user action (double-clicking to jump to source) at a coordinate that maps to the malicious node. Per the advisory-supported conditions, code execution is not guaranteed by SumatraPDF itself and depends on the target editor honoring the injected flags (for example, installing a malicious extension), so this is a moderate, conditional risk rather than a drop-everything priority; no public exploit has been identified at time of analysis, and no fixed release is available as of this review, though an upstream fix commit exists.
Local code execution in SumatraPDF 3.6.1 and earlier on Windows is possible when a user opens an attacker-supplied document and then clicks a link inside a SumatraPDF notification popup, because untrusted text (the document path or a PDF link target) is fed into the notification renderer that interprets '(CmdFoo)' markup as a trusted command link. The injected link dispatches a CmdExec command through ExecuteTipLink(), letting the attacker run a chosen local program with the invoking user's own privileges - no elevation, but also no network exposure, since the malicious file must be opened locally and the injected link must be clicked (UI:R/UI:A, AV:L in both the vendor CVSS 4.0 score of 8.4 and our assessed CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). At time of analysis there is no vendor-released patched version; an upstream fix commit exists, and no public exploit code or KEV-listed active exploitation has been identified.
SumatraPDF versions 3.5.0 through 3.5.2 fail to validate TLS certificates during software updates and execute installers without signature verification, allowing network attackers to perform man-in-the-middle attacks and inject malicious code. An attacker with any valid TLS certificate can intercept update requests and redirect users to a malicious installer, achieving arbitrary code execution on Windows systems. Public exploit code exists for this vulnerability and no patch is currently available.
SumatraPDF 3.5.2 and earlier on Windows allows arbitrary code execution when a user opens a PDF and selects "Show in folder," as the application executes a malicious explorer.exe binary from the same directory without warning. Public exploit code exists for this vulnerability, which affects any user who opens untrusted PDFs and interacts with the file menu option. An attacker can achieve code execution with the privileges of the victim's user account through a simple social engineering attack.
SumatraPDF 3.5.2 and earlier on Windows contains an untrusted search path vulnerability in the Advanced Options feature that allows arbitrary code execution through a malicious notepad.exe placed in the application directory. An attacker with local access can exploit this when a user triggers the Advanced Options setting, as the application fails to specify an absolute path when launching notepad.exe. Public exploit code exists for this vulnerability, and a patch is available.
Opening a malicious CHM (compiled HTML Help) file in SumatraPDF 3.6.1 or earlier crashes the application: unsigned file-controlled string offsets from the /#WINDOWS and /#IVB sections are narrowed to signed integers in ChmFile::GetCharZ() without a lower-bound check, so a negative offset drives a read before the /#STRINGS buffer. Exploitation is local and requires the victim to open the crafted file, and the outcome is limited to a deterministic termination (denial of service) with no code execution, data disclosure, or privilege gain; no public exploit code was identified at time of analysis. Cross-referenced with the advisory and the fixing commit, this is a medium-severity availability issue rather than a high-urgency priority.
Denial of service in SumatraPDF 3.6.1 and earlier, and in pre-release 3.7.0.20369, occurs when the reader falls back to its legacy IE-based HTML/CHM backend - a path taken only when Microsoft WebView2 is absent or cannot initialize - and opens an attacker-crafted CHM file. The signed host component of an its:// URL is accepted by ParseProtoUrl() and then used directly as an index into the gHtmlWindows collection by FindHtmlWindowById(), so a negative or otherwise out-of-range window identifier triggers an out-of-bounds pointer read, an invalid object callback dereference, and termination of the SumatraPDF process. Exploitation is local and requires the victim to open the malicious document (user interaction, unauthenticated per PR:N in the assessed vector); no public exploit code or active exploitation has been identified at time of analysis, and impact is limited to a crash of a single process rather than code execution, data disclosure, or persistence.
Opening a crafted TIFF file in SumatraPDF 3.6.1 and earlier can crash the application through a stack-based buffer overflow in MaybeFlipBitmap(), where GDI+ writes an attacker-controlled EXIF PropertyTagOrientation size into a fixed 64-byte stack buffer. The attack is local and requires the victim to open a malicious image (CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P, base 6.8), and successful exploitation corrupts stack control data that the compiler's stack cookie check intercepts in tested builds, terminating the process. Impact is limited to availability (no confidentiality or integrity loss is claimed), with no confirmed active exploitation (not listed in CISA KEV) and no public exploit identified at time of analysis.
SumatraPDF 3.6.1 and earlier can silently apply no policy restrictions when administrators deploy the file-based sumatrapdfrestrict.ini, because InitializePolicies() initializes gPolicyRestrictions to Perm::All and only ORs permission bits, so the INI can never revoke a permission. A malformed INI or zero-valued permission entries therefore leave intended disk, network, printing, registry, clipboard, preference and fullscreen restrictions open to a local, low-privileged user of that machine, while the alternative -restrict command-line path enforces correctly. No public exploit code identified at time of analysis; exploitation requires local access plus an intentionally configured INI-based lockdown, so default installations that deploy no restriction policy have nothing to bypass.
A local null pointer dereference in SumatraPDF 3.6.1 and earlier lets any process in the same interactive Windows session that runs at an integrity level equal to or higher than SumatraPDF's (the Windows UIPI requirement for sending it inter-process messages) terminate the reader by dispatching a CmdExec command over DDE or WM_COPYDATA while the application sits on its start page with no document tab open. The sole consequence is abrupt process termination and loss of unsaved state; no code execution, data disclosure, or persistence is claimed, and there is no network-reachable vector. No public exploit identified at time of analysis, and no fixed release version was confirmed at review time, although an upstream fix commit and its regression test are publicly visible.
Application termination in SumatraPDF 3.7.0.22298 is reachable when a user opens an attacker-crafted LIT (Microsoft Reader) file, because file-controlled offset and size fields in src/LitDoc.cpp overflow, narrow to negative values, or wrap before incomplete bounds checks, yielding invalid pointer reads and a deterministic crash. The attack path is local and requires the victim to open the malicious document (AV:L/AC:L/PR:N/UI:R, availability-only impact with no confidentiality or integrity loss), and exploitation is further gated by the victim using this specific build and handling the uncommon LIT format. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS data was supplied, so this remains a moderate-severity denial-of-service condition rather than a high-priority memory-corruption or code-execution threat.
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.
Opening a crafted MOBI file in SumatraPDF 3.7.0.22298 triggers an out-of-bounds read that reliably terminates the application with a native access violation. The bug is a signed/unsigned narrowing flaw in src/MobiDoc.cpp: an attacker-supplied mobiHdr.hdrLen value above INT_MAX becomes negative during the upper-bound check, and when the EXTH flag is set that same original unsigned value is reused as a pointer offset, driving DecodeExthHeader() past the end of the record buffer. Only denial of service has been demonstrated - no code execution, information disclosure, or integrity impact - and the CVSS vector (AV:L/PR:N/UI:R, C:N/I:N/A:H) reflects that the victim must actively open the malicious file locally; no public exploit has been identified at time of analysis and this CVE is not in CISA KEV. Several third-party tags (RCE, Information Disclosure, Microsoft) are inconsistent with the technical evidence and the assessed vector and should be discounted.
Opening a crafted MOBI e-book in SumatraPDF versions before 3.6 can crash the application because the MOBI header decoder trusts an attacker-controlled header length and reads past a short heap buffer; the bug is limited to the MOBI parser and requires local file delivery plus the user actively opening the document. It is a memory-safety issue (CWE-125) fixed in 3.6, with no confirmed active exploitation, no public exploit identified at time of analysis, and low real-world priority per available signals despite a 6.8 CVSS 4.0 base score. In CVSS terms the vector is AV:L/PR:N/UI:P, so the attacker is unauthenticated but must get the victim to open a malicious file locally, and the assessed impact is only a client crash (no confidentiality, integrity, or scope impact).
Heap buffer overflow in SumatraPDF 3.6.1 and earlier enables an attacker who delivers a crafted CHM file to corrupt parser heap memory via malformed LZX Huffman code lengths. The PRETREE path in make_decode_table writes internal Huffman tree nodes beyond the 104-entry PRETREE_table boundary into adjacent struct LZXstate heap memory, reachable through the chm_open → chm_retrieve_object → LZXdecompress → BUILD_TABLE call chain. No public exploit or active exploitation is confirmed; arbitrary code execution has not been demonstrated, though the upstream fix commit validates that reliable heap corruption is achievable.
SumatraPDF versions 3.5.2 and earlier are vulnerable to a heap buffer over-read in the MOBI file parser due to incomplete bounds validation in the HuffDic decompressor, allowing attackers to crash the application by opening a malicious .mobi file. Public exploit code exists for this vulnerability. Local user interaction is required to trigger the vulnerability, and while denial of service is the primary impact, the out-of-bounds read could potentially leak sensitive memory contents.
SumatraPDF on Windows is vulnerable to a denial-of-service attack through a maliciously crafted Mobi file that triggers an integer underflow in record validation, causing an out-of-bounds heap read and application crash. The vulnerability stems from an off-by-one error in the PalmDbReader::GetRecord function that only occurs with exactly 2 records, and public exploit code is available. No patch has been released at this time.
A null pointer dereference vulnerability was discovered in SumatraPDF 3.5.2 during the processing of a crafted .djvu file. Rated high severity (CVSS 7.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A buffer overflow in SumatraPDF Reader v3.4.6 allows attackers to cause a Denial of Service (DoS) via a crafted text file. Rated medium severity (CVSS 5.5), this vulnerability is no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Heap-based buffer overflow in SumatraPDF before 2.1 allows remote attackers to execute arbitrary code via a crafted PDF document, a different vulnerability than CVE-2012-4895. Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable. No vendor patch available.
Heap-based buffer overflow in SumatraPDF before 2.1 allows remote attackers to execute arbitrary code via a crafted PDF document, a different vulnerability than CVE-2012-4896. Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable. No vendor patch available.
Argument injection in the AI translation feature of SumatraPDF 3.6.1 and earlier allows text placed in a document selection or clipboard to be interpreted as command-line flags when an agentic CLI backend (Grok, Claude Code, or Codex) is configured as the translation provider. Because the vulnerable code builds the child process command line with quote-only escaping, attacker-controlled text can smuggle in flags that alter the model, working directory, approval mode, or sandbox settings used by the launched CLI. Exploitation is local and requires the user to actively invoke the translate/AI-chat action on the crafted text, and only affects installations where one of those agentic CLI backends is installed and selected; no public exploit code was identified at time of analysis, and the issue is not in CISA KEV.
Command-line argument injection in SumatraPDF 3.5.2 and earlier lets an attacker-controlled SyncTeX source filename escape the quoting of an external editor's command template and inject arbitrary flags when a victim triggers inverse search. The attack is strictly conditional: it requires a PDF paired with a crafted sibling .synctex.gz file, a configured or auto-detected inverse-search editor, and a deliberate user action (double-clicking to jump to source) at a coordinate that maps to the malicious node. Per the advisory-supported conditions, code execution is not guaranteed by SumatraPDF itself and depends on the target editor honoring the injected flags (for example, installing a malicious extension), so this is a moderate, conditional risk rather than a drop-everything priority; no public exploit has been identified at time of analysis, and no fixed release is available as of this review, though an upstream fix commit exists.
Local code execution in SumatraPDF 3.6.1 and earlier on Windows is possible when a user opens an attacker-supplied document and then clicks a link inside a SumatraPDF notification popup, because untrusted text (the document path or a PDF link target) is fed into the notification renderer that interprets '(CmdFoo)' markup as a trusted command link. The injected link dispatches a CmdExec command through ExecuteTipLink(), letting the attacker run a chosen local program with the invoking user's own privileges - no elevation, but also no network exposure, since the malicious file must be opened locally and the injected link must be clicked (UI:R/UI:A, AV:L in both the vendor CVSS 4.0 score of 8.4 and our assessed CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). At time of analysis there is no vendor-released patched version; an upstream fix commit exists, and no public exploit code or KEV-listed active exploitation has been identified.
SumatraPDF versions 3.5.0 through 3.5.2 fail to validate TLS certificates during software updates and execute installers without signature verification, allowing network attackers to perform man-in-the-middle attacks and inject malicious code. An attacker with any valid TLS certificate can intercept update requests and redirect users to a malicious installer, achieving arbitrary code execution on Windows systems. Public exploit code exists for this vulnerability and no patch is currently available.
SumatraPDF 3.5.2 and earlier on Windows allows arbitrary code execution when a user opens a PDF and selects "Show in folder," as the application executes a malicious explorer.exe binary from the same directory without warning. Public exploit code exists for this vulnerability, which affects any user who opens untrusted PDFs and interacts with the file menu option. An attacker can achieve code execution with the privileges of the victim's user account through a simple social engineering attack.
SumatraPDF 3.5.2 and earlier on Windows contains an untrusted search path vulnerability in the Advanced Options feature that allows arbitrary code execution through a malicious notepad.exe placed in the application directory. An attacker with local access can exploit this when a user triggers the Advanced Options setting, as the application fails to specify an absolute path when launching notepad.exe. Public exploit code exists for this vulnerability, and a patch is available.
Opening a malicious CHM (compiled HTML Help) file in SumatraPDF 3.6.1 or earlier crashes the application: unsigned file-controlled string offsets from the /#WINDOWS and /#IVB sections are narrowed to signed integers in ChmFile::GetCharZ() without a lower-bound check, so a negative offset drives a read before the /#STRINGS buffer. Exploitation is local and requires the victim to open the crafted file, and the outcome is limited to a deterministic termination (denial of service) with no code execution, data disclosure, or privilege gain; no public exploit code was identified at time of analysis. Cross-referenced with the advisory and the fixing commit, this is a medium-severity availability issue rather than a high-urgency priority.
Denial of service in SumatraPDF 3.6.1 and earlier, and in pre-release 3.7.0.20369, occurs when the reader falls back to its legacy IE-based HTML/CHM backend - a path taken only when Microsoft WebView2 is absent or cannot initialize - and opens an attacker-crafted CHM file. The signed host component of an its:// URL is accepted by ParseProtoUrl() and then used directly as an index into the gHtmlWindows collection by FindHtmlWindowById(), so a negative or otherwise out-of-range window identifier triggers an out-of-bounds pointer read, an invalid object callback dereference, and termination of the SumatraPDF process. Exploitation is local and requires the victim to open the malicious document (user interaction, unauthenticated per PR:N in the assessed vector); no public exploit code or active exploitation has been identified at time of analysis, and impact is limited to a crash of a single process rather than code execution, data disclosure, or persistence.
Opening a crafted TIFF file in SumatraPDF 3.6.1 and earlier can crash the application through a stack-based buffer overflow in MaybeFlipBitmap(), where GDI+ writes an attacker-controlled EXIF PropertyTagOrientation size into a fixed 64-byte stack buffer. The attack is local and requires the victim to open a malicious image (CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P, base 6.8), and successful exploitation corrupts stack control data that the compiler's stack cookie check intercepts in tested builds, terminating the process. Impact is limited to availability (no confidentiality or integrity loss is claimed), with no confirmed active exploitation (not listed in CISA KEV) and no public exploit identified at time of analysis.
SumatraPDF 3.6.1 and earlier can silently apply no policy restrictions when administrators deploy the file-based sumatrapdfrestrict.ini, because InitializePolicies() initializes gPolicyRestrictions to Perm::All and only ORs permission bits, so the INI can never revoke a permission. A malformed INI or zero-valued permission entries therefore leave intended disk, network, printing, registry, clipboard, preference and fullscreen restrictions open to a local, low-privileged user of that machine, while the alternative -restrict command-line path enforces correctly. No public exploit code identified at time of analysis; exploitation requires local access plus an intentionally configured INI-based lockdown, so default installations that deploy no restriction policy have nothing to bypass.
A local null pointer dereference in SumatraPDF 3.6.1 and earlier lets any process in the same interactive Windows session that runs at an integrity level equal to or higher than SumatraPDF's (the Windows UIPI requirement for sending it inter-process messages) terminate the reader by dispatching a CmdExec command over DDE or WM_COPYDATA while the application sits on its start page with no document tab open. The sole consequence is abrupt process termination and loss of unsaved state; no code execution, data disclosure, or persistence is claimed, and there is no network-reachable vector. No public exploit identified at time of analysis, and no fixed release version was confirmed at review time, although an upstream fix commit and its regression test are publicly visible.
Application termination in SumatraPDF 3.7.0.22298 is reachable when a user opens an attacker-crafted LIT (Microsoft Reader) file, because file-controlled offset and size fields in src/LitDoc.cpp overflow, narrow to negative values, or wrap before incomplete bounds checks, yielding invalid pointer reads and a deterministic crash. The attack path is local and requires the victim to open the malicious document (AV:L/AC:L/PR:N/UI:R, availability-only impact with no confidentiality or integrity loss), and exploitation is further gated by the victim using this specific build and handling the uncommon LIT format. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS data was supplied, so this remains a moderate-severity denial-of-service condition rather than a high-priority memory-corruption or code-execution threat.
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.
Opening a crafted MOBI file in SumatraPDF 3.7.0.22298 triggers an out-of-bounds read that reliably terminates the application with a native access violation. The bug is a signed/unsigned narrowing flaw in src/MobiDoc.cpp: an attacker-supplied mobiHdr.hdrLen value above INT_MAX becomes negative during the upper-bound check, and when the EXTH flag is set that same original unsigned value is reused as a pointer offset, driving DecodeExthHeader() past the end of the record buffer. Only denial of service has been demonstrated - no code execution, information disclosure, or integrity impact - and the CVSS vector (AV:L/PR:N/UI:R, C:N/I:N/A:H) reflects that the victim must actively open the malicious file locally; no public exploit has been identified at time of analysis and this CVE is not in CISA KEV. Several third-party tags (RCE, Information Disclosure, Microsoft) are inconsistent with the technical evidence and the assessed vector and should be discounted.
Opening a crafted MOBI e-book in SumatraPDF versions before 3.6 can crash the application because the MOBI header decoder trusts an attacker-controlled header length and reads past a short heap buffer; the bug is limited to the MOBI parser and requires local file delivery plus the user actively opening the document. It is a memory-safety issue (CWE-125) fixed in 3.6, with no confirmed active exploitation, no public exploit identified at time of analysis, and low real-world priority per available signals despite a 6.8 CVSS 4.0 base score. In CVSS terms the vector is AV:L/PR:N/UI:P, so the attacker is unauthenticated but must get the victim to open a malicious file locally, and the assessed impact is only a client crash (no confidentiality, integrity, or scope impact).
Heap buffer overflow in SumatraPDF 3.6.1 and earlier enables an attacker who delivers a crafted CHM file to corrupt parser heap memory via malformed LZX Huffman code lengths. The PRETREE path in make_decode_table writes internal Huffman tree nodes beyond the 104-entry PRETREE_table boundary into adjacent struct LZXstate heap memory, reachable through the chm_open → chm_retrieve_object → LZXdecompress → BUILD_TABLE call chain. No public exploit or active exploitation is confirmed; arbitrary code execution has not been demonstrated, though the upstream fix commit validates that reliable heap corruption is achievable.
SumatraPDF versions 3.5.2 and earlier are vulnerable to a heap buffer over-read in the MOBI file parser due to incomplete bounds validation in the HuffDic decompressor, allowing attackers to crash the application by opening a malicious .mobi file. Public exploit code exists for this vulnerability. Local user interaction is required to trigger the vulnerability, and while denial of service is the primary impact, the out-of-bounds read could potentially leak sensitive memory contents.
SumatraPDF on Windows is vulnerable to a denial-of-service attack through a maliciously crafted Mobi file that triggers an integer underflow in record validation, causing an out-of-bounds heap read and application crash. The vulnerability stems from an off-by-one error in the PalmDbReader::GetRecord function that only occurs with exactly 2 records, and public exploit code is available. No patch has been released at this time.
A null pointer dereference vulnerability was discovered in SumatraPDF 3.5.2 during the processing of a crafted .djvu file. Rated high severity (CVSS 7.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A buffer overflow in SumatraPDF Reader v3.4.6 allows attackers to cause a Denial of Service (DoS) via a crafted text file. Rated medium severity (CVSS 5.5), this vulnerability is no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Heap-based buffer overflow in SumatraPDF before 2.1 allows remote attackers to execute arbitrary code via a crafted PDF document, a different vulnerability than CVE-2012-4895. Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable. No vendor patch available.
Heap-based buffer overflow in SumatraPDF before 2.1 allows remote attackers to execute arbitrary code via a crafted PDF document, a different vulnerability than CVE-2012-4896. Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable. No vendor patch available.