Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft PDF with malformed U3D/GIF texture dimensions
-
DeliveryDeliver via phishing email or web link
-
ExploitVictim opens file in Foxit Reader/Editor
-
ExecutionDecoder makes undersized allocation
-
PersistOut-of-bounds write corrupts memory
-
ImpactExecute arbitrary code in app context
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation 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 PDF in Foxit PDF Editor or Reader that embeds a malicious U3D 3D model or GIF image whose texture dimension/size metadata is manipulated to force an incorrectly sized allocation. Limiting factors: mandatory user interaction (UI:R - the victim must open the document), the local delivery/processing model (AV:L), and the requirement that the specific U3D/GIF texture-decoding code path be reached during rendering. The description's 'under certain conditions' qualifier suggests the OOB write is not triggered by all malformed textures, which may further constrain reliable exploitation. No authentication is required against the application itself (PR:N). |
| Impact | This is a genuine high-priority client-side memory-corruption flaw, though not an emergency at time of analysis. The vendor CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 7.8) is internally consistent for a file-parsing bug: AV:L reflects that the malicious PDF must be delivered to and opened on the victim's machine (the file itself is the local attack surface), and UI:R correctly captures the required victim action of opening the document. The CWE-787 out-of-bounds write with a mis-sized allocation is a classic exploitable primitive, and the description's 'potentially resulting in remote code execution' supports the full C:H/I:H/A:H impact ceiling. However, several exploitation signals are MISSING: no EPSS score is provided, the CVE is NOT listed in CISA KEV, and no public exploit code is referenced - the only reference is Foxit's generic security-bulletins.html landing page with no version data, patch identifier, or technical writeup. So while the technical ceiling (RCE) is high, there is no evidence of real-world exploitation and no confirmed PoC, placing realistic near-term risk below what the 7.8 alone implies. Note the AV:L designation is standard for PDF-parsing CVEs but can be misread as 'requires local login' - it does not; a remote attacker delivers the file (email/web) and the local vector reflects that processing happens on the victim host. |
| Exploit ScenarioDerived | An attacker crafts a PDF containing a malicious U3D 3D object or embedded GIF texture with manipulated image-dimension/size fields, then delivers it via phishing email or a web download. When the victim opens the document in Foxit PDF Editor or Reader, the texture decoder allocates an undersized buffer and writes attacker-controlled pixel data out of bounds, corrupting memory and potentially yielding code execution in the application's context. No public proof-of-concept is referenced, so exploitation would currently require independent development of a working exploit. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Out-of-bounds write in the U3D/GIF texture decoding path of Foxit PDF Editor and Foxit PDF Reader allows a crafted PDF to corrupt process memory and potentially achieve remote code execution when the victim opens the file. Exploitation requires user interaction (the document must be opened and the malicious 3D model or GIF texture must actually be rendered) and is delivered through the local file/processing path (AV:L), while no application-level authentication is required (PR:N). No confirmed active exploitation and no public exploit code were identified at time of analysis; Foxit directs users to its security bulletins page for version guidance.
RemediationAI
Patch status cannot be confirmed from the supplied data beyond the vendor's general security bulletin page, so the primary action is to check https://www.foxit.com/support/security-bulletins.html and install the most recent Foxit PDF Editor/Reader release listed there; if no fixing release is documented for your version, upgrade to the newest available build and monitor the bulletin page for the specific fixed version. As compensating controls while unpatched, enable Foxit's Safe Reading Mode / Trust Manager so that embedded 3D (U3D) content and other active elements are not processed automatically from untrusted documents (trade-off: legitimate 3D PDFs will not render until the document is trusted), disable or restrict 3D/embedded-media rendering in the application preferences if your workflows do not require it, and avoid opening PDFs from untrusted sources. Because exploitation requires the victim to open a crafted file locally, run Foxit in a sandboxed or low-privilege context and keep operating-system exploit mitigations such as ASLR, DEP, and CFG enabled to complicate reliable code execution; these controls reduce risk but do not eliminate the underlying memory-corruption bug, so patching remains the definitive fix.
Affected VersionsENISA
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 vulnerability is a CWE-787 out-of-bounds write rooted in the parsing of embedded U3D (Universal 3D) models and GIF images inside PDF documents. During texture decoding, Foxit PDF Editor and Reader derive buffer sizes from image dimension and related size fields contained in the file without sufficiently validating those values against actual pixel data. A manipulated dimension or size field causes an allocation that is smaller than what the subsequent pixel-processing loop writes, producing a heap/out-of-bounds write of attacker-influenced data. This is a classic client-side parser memory-corruption pattern: the attacker controls file content but exploitation depends on the rendering code path being reached and on the specific malformed texture satisfying the 'certain conditions' noted by the vendor, meaning not every malformed texture will reliably trigger the write. The CPE data covers both foxit_pdf_editor and foxit_pdf_reader, confirming the shared decoding engine is affected across the product family.
Know when Foxit Pdf Editor 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:H/I:H/A:H
Local file-parsing OOB write requiring the victim to open a crafted PDF (AV:L/UI:R), no prior privileges (PR:N), with RCE yielding full C/I/A within the app process (S:U).
Primary rating from Vendor (Foxit).
CVSS VectorVendor: Foxit
DescriptionCVE.org
Foxit PDF Editor/Reader’s U3D/GIF texture decoding path contained insufficient validation of image dimensions and related size information. Under certain conditions, this could lead to an incorrectly sized memory allocation and a subsequent out-of-bounds write during pixel processing, potentially resulting in remote code execution.
Zero Day Initiative Advisories
Executive ViewAI
Foxit PDF Editor and Foxit PDF Reader are affected by a high-severity out-of-bounds write vulnerability (CVE-2026-91789) that could allow remote code execution when a user opens a malicious PDF containing a crafted 3D model or GIF texture. With no vendor-released patch identified at time of analysis and no public exploit identified at time of analysis, the primary risk is to employees who open untrusted PDFs, potentially leading to system compromise and data breach. Leadership should prioritize immediate user awareness and consider interim controls to reduce exposure until a fix is released.
No vendor-released patch identified at time of analysis. Interim mitigations include: user education to avoid opening untrusted PDFs, especially those with 3D models or GIF textures; enabling endpoint protection and sandboxing for PDF readers; restricting the use of Foxit for untrusted documents; and monitoring Foxit security bulletins for updates.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Foxit Pdf Editor
View allContent spoofing in Foxit PDF Editor and Foxit PDF Reader allows remote attackers to alter visible content in incrementa
Local privilege escalation in Foxit PDF Editor for macOS allows an attacker with a low-privilege foothold to execute arb
A local privilege escalation vulnerability in the auto-update daemon shipped with Foxit PDF Editor and Foxit PDF Reader
Man-in-the-middle attackers occupying the network path of Foxit PDF Editor and Foxit PDF Reader software-update traffic
Path traversal in the attachment-handling logic of Foxit PDF Editor and Foxit PDF Reader lets a crafted PDF write an emb
An out-of-bounds write (CWE-787) in the PDF rendering engine of Foxit PDF Editor and Foxit PDF Reader can be triggered w
Insufficient validation of embedded-resource file paths in Foxit PDF Editor and Foxit PDF Reader (CVE-2026-91801) lets a
Foxit PDF Editor and Reader can crash due to a use-after-free (CWE-416) when a user opens a specially crafted PDF that i
Use-after-free in Foxit PDF Editor and Foxit PDF Reader (CWE-416) lets a specially crafted PDF trigger memory corruption
Heap-based out-of-bounds write in Foxit PDF Editor and Foxit PDF Reader occurs when the products decode JPEG2000 image d
A use-after-free in Foxit PDF Editor and Foxit PDF Reader can be triggered by opening a crafted PDF whose image objects
Specially crafted PDFs can trigger a use-after-free in Foxit PDF Reader and Editor when JavaScript is enabled, leading t
EUVD-2026-85155
GHSA-h787-m92q-vv52
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB