Application crash via uninitialized file-stream dereference
Published Dec 9, 2025 · Updated Dec 11, 2025
NULL pointer dereference in PDF-XChange Editor 10.7.3.401 allows context-dependent attackers to crash the application via a crafted PDF. The util.readFileIntoStream method leaves a file-stream object zeroed when stream creation fails, then dereferences that uninitialized object. A user must open the malicious PDF; exploitation terminates the editor without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in PDF-XChange Editor 10.7.3.401 allows context-dependent attackers to crash the application via a crafted PDF. The util.readFileIntoStream method leaves a file-stream object zeroed when stream creation fails, then dereferences that uninitialized object. A user must open the malicious PDF; exploitation terminates the editor without reported data disclosure or modification.
The record
- CVE
- CVE-2025-64086
- Published
- Dec 9, 2025
- Updated
- Dec 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- Dec 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- util.readFileIntoStream crash proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo