CVE-2025-69627

HighCVSS 8.4

Published: 13/04/2026(UTC)Updated: 05/07/2026(UTC)Translated: 06/07/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.20%

10th percentile - higher than 10% of all known CVEs

Summary

Nitro PDF Pro for Windows version 14.41.1.4 contains a heap use-after-free vulnerability in the implementation of the JavaScript method this.mailDoc(). During execution, an internal XID object is allocated and then freed prematurely, after which the freed pointer is still passed into UI and logging helper functions. This can result in access violations and non-deterministic crashes.

Risk Assessment

The risk for the organization includes potential application crashes and possible code execution by an attacker through heap manipulation, which could lead to data confidentiality or integrity breaches.

Recommendation

It is recommended to immediately update Nitro PDF Pro to the latest version that fixes this vulnerability. Until the update is applied, avoid opening untrusted PDF documents containing JavaScript scripts.

Other vulnerabilities in Nitro PDF Pro

CVE-2025-69624High
The vulnerability in Nitro PDF Pro for Windows before version 14.43 is a NULL pointer dereference in the JavaScript implementation of the app.alert() function. Calling app.alert() with more than one argument where the first argument evaluates to null (e.g., app.alert(app.activeDocs, true) when app.activeDocs is null) causes the engine to route through a fallback path for non-string arguments. In this path, js_ValueToString() returns an invalid string pointer, which is then passed to JS_GetStringChars() without validation, leading to an access violation and application crash when opening a crafted PDF.

Original NVD description (English source)

Nitro PDF Pro for Windows 14.41.1.4 contains a heap use-after-free vulnerability in the implementation of the JavaScript method this.mailDoc(). During execution, an internal XID object is allocated and then freed prematurely, after which the freed pointer is still passed into UI and logging helper functions. Because the freed memory region may contain unpredictable heap data or remnants of attacker-controlled JavaScript strings, downstream routines such as wcscmp() may process invalid or stale pointers. This can result in access violations and non-deterministic crashes.