Safeguard
Vulnerability Analysis•

CVE-2023-32159: High PDF File Out-of-Bounds Write in Editor

CVE-2023-32159 is a high (CVSS 7.8) PDF parsing out-of-bounds write in PDF-XChange Editor 9.3.361.0. Update to the latest vendor release, then recheck.

Safeguard Security Team
4 min read

CVE-2023-32159 is a high severity out-of-bounds write, scored 7.8, in PDF file parsing in PDF-XChange Editor. A crafted PDF can run code once opened. The record names build 9.3.361.0 and the vendor has issued an update, so move to the newest 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-641 (ZDI-CAN-17765) 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

  1. Find every PDF-XChange Editor installation and note its build number.
  2. Update to the current release from the vendor, and check the vendor's security bulletins for fixes that name this CVE.
  3. Until updated, do not open PDF files from unknown senders in Editor. Use a different, updated reader for untrusted files.
  4. Turn off automatic opening of downloaded PDFs in browsers set to launch Editor.
  5. Add Editor to your software inventory so future builds are tracked.

Why it matters

This is the second of four near-identical CWE-787 reports against the same PDF parser. ZDI tracks them separately as ZDI-CAN-17764, 17765, 17767 and 17778, so they are different defects even though the description matches. A scanner or ticket system that merges them by title would hide the count.

The consequence is the same for each: code runs with the rights of the person who opened the file. On a locked down user account that is limited, and on an administrator account it is not. Running document tools as a standard user is a cheap control that reduces all four. 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.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Are these four PDF-XChange CVEs really different?

ZDI tracks them under different identifiers, so they are separate defects with matching descriptions. This one is ZDI-CAN-17765.

Is there a workaround?

The sources list none. Update, and avoid opening untrusted PDFs in the affected build.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.