When the application opens a PDF file, JavaScript uses the damaged field tree to trigger field traversal, resulting in the program holding an invalid form object when accessing the field property path. Eventually, the application crashes due to reading an invalid pointer.
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.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Pdf_editor | Foxit | * | 13.2.4.24048 (including) |
| Pdf_editor | Foxit | 14.0.0.33046 (including) | 14.0.4.33508 (including) |
| Pdf_editor | Foxit | 2023.1.0.15510 (including) | 2023.3.0.23028 (including) |
| Pdf_editor | Foxit | 2024.1.0.23997 (including) | 2024.4.1.27687 (including) |
| Pdf_editor | Foxit | 2025.1.0.27937 (including) | 2025.3.0.35737 (including) |
| Pdf_editor | Foxit | 2026.1.0.36452 (including) | 2026.1.1.36485 (including) |
| Pdf_reader | Foxit | * | 2026.1.1.36485 (including) |