CVE-2025-66494
BaseFortify
Publication date: 2025-12-19
Last updated on: 2025-12-23
Assigner: Foxit
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| foxit | pdf_editor | to 13.2.1.23955 (inc) |
| foxit | pdf_editor | From 14.0.0.33046 (inc) to 14.0.1.33197 (inc) |
| foxit | pdf_editor | From 2023.1.0.15510 (inc) to 2023.3.0.23028 (inc) |
| foxit | pdf_editor | From 2024.1.0.23997 (inc) to 2024.4.1.27687 (inc) |
| foxit | pdf_editor | From 2025.1.0.27937 (inc) to 2025.2.1.33197 (inc) |
| foxit | pdf_reader | to 2025.2.1.33197 (inc) |
| microsoft | windows | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free issue in the PDF file parsing component of Foxit PDF Reader versions before 2025.2.1, 14.0.1, and 13.2.1 on Windows. It occurs when a PDF object that is managed by multiple parent objects is freed while it is still being referenced, which can lead to memory corruption and potentially allow a remote attacker to execute arbitrary code.
How can this vulnerability impact me? :
The vulnerability can allow a remote attacker to execute arbitrary code on the affected system, which could lead to full compromise of the system, including data theft, system control, or further malware installation.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update Foxit PDF Reader to version 2025.2.1, 14.0.1, 13.2.1 or later on Windows to ensure the use-after-free issue in PDF parsing is fixed.