Use-After-Free Vulnerability in UI Refresh Causes Application Crashes

Publication date: 2026-04-27

Last updated on: 2026-04-29

Assigner: Foxit

Description

Calling a function that triggers a UI refresh after removing comments via a script may access an invalidated object, leading to program crashes.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-04-27

Last Modified

2026-04-29

Generated

2026-07-06

AI Q&A

2026-04-27

EPSS Evaluated

2026-07-05

NVD

CVE-2026-5940

EUVD

EUVD-2026-25826

Affected Vendors & Products

Vendor	Product	Version / Range
foxit	pdf_editor	to 13.2.4 (exc)
foxit	pdf_editor	From 14.0.0 (inc) to 14.0.4 (exc)
foxit	pdf_editor	From 2023.0.0 (inc) to 2026.1.1 (exc)
foxit	pdf_reader	to 2026.1.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

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

Executive Summary

This vulnerability occurs when a function that triggers a user interface (UI) refresh is called after comments have been removed via a script. The problem is that this function may try to access an object that has already been invalidated or removed, which can cause the program to crash.

Impact Analysis

The impact of this vulnerability includes potential program crashes due to accessing invalidated objects during UI refresh. This can lead to denial of service or loss of availability of the affected software.

Hi! I’m here to help you understand CVE-2026-5940. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70