PDF Reader
CVEs (537)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-57249 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | After the application opened the PDF file, the script first reset the annotation status, then triggered the reset form event by additional action. During the re-entry process, the application access invalid objects and crashed. | ||
| CVE-2026-57248 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | When the application opens a PDF file and JavaScript writes annotation attributes, there is a lack of sufficient object type and argument checks. As a result, due to the damage to the internal structure of the annotations, it causes the application to crash during subsequent… | ||
| CVE-2026-57247 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | The application re-enters the document structure via field processing and deletes the current page, and then continues using the field objects obtained before deletion, triggering an illegal read and crashing. | ||
| CVE-2026-57246 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | When dealing with abnormally constructed objects, there is a lack of argument validation; JavaScript triggers signature verification, but the signature plugin does not perform validation when copying the abnormal string, causing the application to crash. | ||
| CVE-2026-57245 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | When the application opens a PDF, traverses and builds the annotation elements related to hyperlinks, it fails to validate the abnormal annotation relationships and field combinations. This results in the internal objects entering an invalid state. Eventually, during the… | ||
| CVE-2026-57244 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | After JavaScript resetting the form, the synchronization process lacks re-entry protection and object lifecycle verification, resulting in the failure of the control pointer during the traversal process. After the pointer fails, it still continues to dereference, causing the… | ||
| CVE-2026-57243 | Med | 0.00 | 6.1 | 0.00 | Jul 8, 2026 | During the process of page opening and form formatting, a JavaScript reentrancy results in an inconsistent document status. Subsequently, with outdated page information, the application attempts to access invalid addresses, causing the application to crash. | ||
| CVE-2026-57242 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | The application opens the PDF, and JavaScript modifies the form. However, the related objects on the page lack complete lifecycle management and null value validation; when the page state changes, the application continuously dereferences invalid objects, eventually leading to a… | ||
| CVE-2026-57241 | Med | 0.00 | 6.1 | 0.00 | Jul 8, 2026 | The application opens the PDF, and JavaScript performs operations on the page and the document, causing the page-related objects within the application to lose synchronization; however, the renderer still trusts the outdated page count, and eventually the application crashes due… | ||
| CVE-2026-57240 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | When the application opens a PDF file and JavaScript deletes the PDF fields, the subsequent logic still uses the old field pointers, resulting in invalid pointer references and causing the application to crash. | ||
| CVE-2026-57239 | Hig | 0.00 | 8.2 | 0.00 | Jul 8, 2026 | The user-controllable executable files will be directly executed by high-privilege processes, allowing low-privilege users to have the opportunity to elevate their privileges to NT AUTHORITY\SYSTEM. | ||
| CVE-2026-57238 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | After the application opened the PDF, JavaScript deleted the form field object. Subsequently, it attempted to access the invalid object, which caused the application to crash. | ||
| CVE-2026-57237 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | When the application opens a PDF and JavaScript modifies the properties of form fields, it causes the state of the underlying objects referenced by the program to become invalid. Eventually, it reads an illegal memory address, which leads to the crash of the application. | ||
| CVE-2026-13129 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | 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. | ||
| CVE-2026-13128 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | Embedding JavaScript within a PDF file will cause the page to be deleted. Subsequent scripts will continue to access the relevant properties of the document view, eventually leading to the crash of the application. | ||
| CVE-2026-13127 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | The application opens the PDF file. JavaScript then rewrites the document to modify the page structure, resulting in the invalidation of the page objects. However, the thumbnails still use the invalid page objects, ultimately causing the application to crash. | ||
| CVE-2026-13126 | Hig | 0.00 | 7.8 | 0.00 | Jul 8, 2026 | The embedded JavaScript in the PDF deleted the pages, making the object invalid. The application attempted to perform a write operation on the invalid pop-up annotations, resulting in the program crashing. |
- risk 0.00cvss 7.8epss 0.00
After the application opened the PDF file, the script first reset the annotation status, then triggered the reset form event by additional action. During the re-entry process, the application access invalid objects and crashed.
- risk 0.00cvss 7.8epss 0.00
When the application opens a PDF file and JavaScript writes annotation attributes, there is a lack of sufficient object type and argument checks. As a result, due to the damage to the internal structure of the annotations, it causes the application to crash during subsequent…
- risk 0.00cvss 7.8epss 0.00
The application re-enters the document structure via field processing and deletes the current page, and then continues using the field objects obtained before deletion, triggering an illegal read and crashing.
- risk 0.00cvss 7.8epss 0.00
When dealing with abnormally constructed objects, there is a lack of argument validation; JavaScript triggers signature verification, but the signature plugin does not perform validation when copying the abnormal string, causing the application to crash.
- risk 0.00cvss 7.8epss 0.00
When the application opens a PDF, traverses and builds the annotation elements related to hyperlinks, it fails to validate the abnormal annotation relationships and field combinations. This results in the internal objects entering an invalid state. Eventually, during the…
- risk 0.00cvss 7.8epss 0.00
After JavaScript resetting the form, the synchronization process lacks re-entry protection and object lifecycle verification, resulting in the failure of the control pointer during the traversal process. After the pointer fails, it still continues to dereference, causing the…
- risk 0.00cvss 6.1epss 0.00
During the process of page opening and form formatting, a JavaScript reentrancy results in an inconsistent document status. Subsequently, with outdated page information, the application attempts to access invalid addresses, causing the application to crash.
- risk 0.00cvss 7.8epss 0.00
The application opens the PDF, and JavaScript modifies the form. However, the related objects on the page lack complete lifecycle management and null value validation; when the page state changes, the application continuously dereferences invalid objects, eventually leading to a…
- risk 0.00cvss 6.1epss 0.00
The application opens the PDF, and JavaScript performs operations on the page and the document, causing the page-related objects within the application to lose synchronization; however, the renderer still trusts the outdated page count, and eventually the application crashes due…
- risk 0.00cvss 7.8epss 0.00
When the application opens a PDF file and JavaScript deletes the PDF fields, the subsequent logic still uses the old field pointers, resulting in invalid pointer references and causing the application to crash.
- risk 0.00cvss 8.2epss 0.00
The user-controllable executable files will be directly executed by high-privilege processes, allowing low-privilege users to have the opportunity to elevate their privileges to NT AUTHORITY\SYSTEM.
- risk 0.00cvss 7.8epss 0.00
After the application opened the PDF, JavaScript deleted the form field object. Subsequently, it attempted to access the invalid object, which caused the application to crash.
- risk 0.00cvss 7.8epss 0.00
When the application opens a PDF and JavaScript modifies the properties of form fields, it causes the state of the underlying objects referenced by the program to become invalid. Eventually, it reads an illegal memory address, which leads to the crash of the application.
- risk 0.00cvss 7.8epss 0.00
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.
- risk 0.00cvss 7.8epss 0.00
Embedding JavaScript within a PDF file will cause the page to be deleted. Subsequent scripts will continue to access the relevant properties of the document view, eventually leading to the crash of the application.
- risk 0.00cvss 7.8epss 0.00
The application opens the PDF file. JavaScript then rewrites the document to modify the page structure, resulting in the invalidation of the page objects. However, the thumbnails still use the invalid page objects, ultimately causing the application to crash.
- risk 0.00cvss 7.8epss 0.00
The embedded JavaScript in the PDF deleted the pages, making the object invalid. The application attempted to perform a write operation on the invalid pop-up annotations, resulting in the program crashing.
Page 27 of 27