CVE-2023-32160 is a high severity out-of-bounds write, scored 7.8, in how PDF-XChange Editor reads PDF files. A crafted file can run code when opened. The record names build 9.3.361.0, and the vendor says it has issued an update, so install the latest release.
What's affected
The NVD record, dated 2024-05-03, says PDF-XChange Editor has an out-of-bounds write (CWE-787) in PDF file parsing that allows remote code execution. The record's product data names PDF-XChange Editor and PDF-XChange PDF-Tools at version 9.3.361.0. The vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, scored 7.8.
ZDI advisory ZDI-23-642 (ZDI-CAN-17767) confirms the description: crafted data in a PDF file can trigger a write past the end of an allocated buffer, and an attacker can execute code in the context of the current process. The user must open a malicious file or visit a malicious page. ZDI reported it to the vendor on 2022-07-13 and published on 2023-05-17.
ZDI and NVD agree on the score, 7.8. The fix is less clear. ZDI says only that PDF-XChange has issued an update and points to the vendor's version history. The version history page we fetched does not mention this flaw or the ZDI identifiers, so we cannot name the first fixed build. Check the vendor's security bulletins and make sure you run the current release.
No source says this flaw is exploited in the wild, and it is not in the CISA Known Exploited Vulnerabilities catalog.
How to check if you're exposed
Open PDF-XChange Editor, go to the Help menu and choose About to read the build number. The record names 9.3.361.0. If you run that build or an older one, treat it as affected.
Check Editor installations on every machine, including portable copies and builds bundled into other software, since the PDF-Tools component is also named in the record. The vendor's version history page lists release notes and a security bulletins link, which is the place to confirm which build fixes the issue.
If you cannot confirm a fixed build, install the latest release from the vendor.
What to do now
- Find every PDF-XChange Editor installation and note its build number.
- Update to the current release from the vendor, and check the vendor's security bulletins for fixes that name this CVE.
- Until updated, do not open PDF files from unknown senders in Editor. Use a different, updated reader for untrusted files.
- Turn off automatic opening of downloaded PDFs in browsers set to launch Editor.
- Add Editor to your software inventory so future builds are tracked.
Why it matters
The third report in a series of four, this one is ZDI-CAN-17767. All four are CWE-787 in the PDF parser, and the advisory text is identical apart from the identifier. When a vendor receives several reports of the same class in one component, it often points to code that was not written with bounds checks as a habit, which makes a full update more reliable than waiting for a single fix.
For defenders the plan does not change per CVE: find the installs, update, and limit exposure to untrusted PDFs. Safeguard offers a free in-browser dependency scan at gold.safeguard.sh/scan for the packages in your own code. It does not inspect vehicle firmware or installed desktop applications, so those need a separate inventory.
Quick check
What is the attack path?
A person opens a crafted PDF, or visits a page that leads Editor to open one. The vector is local with required user interaction.
Where do I confirm the fix?
Use the vendor security bulletins and version history that ZDI points to. They are the source for fixed build numbers.
Sources
Last reviewed: 19 October 2026.