PDF Editor/Reader
CVEs (26)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-57244 | 0.00 | — | 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-57247 | 0.00 | — | 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-57250 | 0.00 | — | 0.00 | Jul 8, 2026 | When the application opens a PDF and JavaScript resets the form fields, the script re-enters the interface. The underlying native object is damaged, but the application does not perform validation. The function call on the damaged object leads to the application crashing. | |||
| CVE-2026-57257 | 0.00 | — | 0.00 | Jul 8, 2026 | During the PRC parsing stage, there is a lack of boundary verification for the PRC entity index, which leads to an out-of-bounds read of the entity array. As a result, the application crashes. | |||
| CVE-2026-57258 | 0.00 | — | 0.00 | Jul 8, 2026 | The PRC file header parsing logic trusts the constructed file structure description information, assumes that the underlying array contains elements and reads them, leading to out-of-bounds reads and application crashes. | |||
| CVE-2026-57260 | 0.00 | — | 0.00 | Jul 8, 2026 | The application opened a PDF file containing an abnormal Unity 3D object. During parsing, the application incorrectly resolved a portion of the abnormal object as a pointer and used it as a valid address, ultimately causing the application to crash. |
- CVE-2026-57244Jul 8, 2026risk 0.00cvss —epss 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…
- CVE-2026-57247Jul 8, 2026risk 0.00cvss —epss 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.
- CVE-2026-57250Jul 8, 2026risk 0.00cvss —epss 0.00
When the application opens a PDF and JavaScript resets the form fields, the script re-enters the interface. The underlying native object is damaged, but the application does not perform validation. The function call on the damaged object leads to the application crashing.
- CVE-2026-57257Jul 8, 2026risk 0.00cvss —epss 0.00
During the PRC parsing stage, there is a lack of boundary verification for the PRC entity index, which leads to an out-of-bounds read of the entity array. As a result, the application crashes.
- CVE-2026-57258Jul 8, 2026risk 0.00cvss —epss 0.00
The PRC file header parsing logic trusts the constructed file structure description information, assumes that the underlying array contains elements and reads them, leading to out-of-bounds reads and application crashes.
- CVE-2026-57260Jul 8, 2026risk 0.00cvss —epss 0.00
The application opened a PDF file containing an abnormal Unity 3D object. During parsing, the application incorrectly resolved a portion of the abnormal object as a pointer and used it as a valid address, ultimately causing the application to crash.
Page 2 of 2