CVE-2023-32158 is a high severity out-of-bounds write, scored 7.8, in the way PDF-XChange Editor parses PDF files. Opening a crafted file can run code. The record names build 9.3.361.0, and the vendor 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-640 (ZDI-CAN-17764) 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
CWE-787 means the program writes outside memory it reserved. PDF files are a rich format with many object types, so parsers are large and a common home for these bugs. Editors that open files from email and the web are in the path of untrusted data every day, which is why a flaw like this carries weight even though a user must open the file.
This is the first of four PDF parsing write bugs, ZDI-CAN-17764, 17765, 17767 and 17778, reported on the same advisory date. The vendor update addresses them together, and running a current build is the sensible position. 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
Do I have to open a file for it to work?
Yes. ZDI says user interaction is required: the target must open a malicious file or visit a malicious page.
Which build fixes it?
The sources do not name one. ZDI points to the vendor version history, so check the vendor security bulletins and run the latest release.
Sources
Last reviewed: 19 October 2026.