CVE-2023-27340 is a high severity (CVSS 7.8) out-of-bounds write in how PDF-XChange Editor handles PNG images. Opening a crafted file could lead to code execution. Update to the newest Editor build, and check the vendor history page for the build that carries the fix.
What's affected
The record lists PDF-XChange Editor build 9.4.364.0, and the PDF-Tools package built from the same code. The Zero Day Initiative advisory ZDI-23-352 says the vendor has issued an update and points to the vendor's version history page. It does not give a fixed build number, and I could not find one in the pages I could read. Treat the fixed version as unconfirmed and read the version history yourself.
The score is consistent across sources. The record and ZDI both show 7.8 with a local attack vector, low complexity, no privileges and user interaction required. High impact is rated for confidentiality, integrity and availability. "Local" here means the file is opened on the victim's machine, even though the advisory text also says the target must visit a malicious page or open a malicious file.
Like its sibling CVE-2023-27339, this flaw is in the parsing of PNG files. Crafted data in a PNG can trigger a write past the end of an allocated buffer. ZDI treats it as a separate bug with its own advisory number. The weakness class is CWE-787. ZDI says the code runs in the context of the current process, so the attacker gets the rights of the user who opened the file. The advisory dates the vendor report to 28 September 2022, with public release on 31 March 2023.
How to check if you're exposed
PDF-XChange Editor is a Windows desktop application. Read the installed version from Help, then About inside the application, or inventory it with PowerShell:
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*,
HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* |
Where-Object DisplayName -like "*PDF-XChange*" |
Select-Object DisplayName, DisplayVersion
The record names build 9.4.364.0 for the Editor and for the PDF-Tools package that shares its code. I could not read which later build fixed this issue, because the vendor's version history page only showed its newest entries in the text available to me. Open that page, search for the item that matches the advisory, and note the build number. Then compare it with what your inventory reports. Treat anything older than that build as exposed.
To see which of your own applications pull in affected components, run the free in-browser dependency scan at gold.safeguard.sh/scan.
What to do now
- Find all machines with PDF-XChange Editor or PDF-Tools and record their build numbers.
- Update to the current release from the vendor, and confirm the fix entry in the version history.
- Turn on automatic updates for the application where your policy allows.
- Tell users to open PDF-related files only from sources they trust until the update lands.
- Remove the application from machines that do not need it.
Why it matters
Two CVEs with one description often mean two distinct code paths. Fixing one does not prove the other is fixed, so confirm the build you deploy covers both ZDI-23-351 and ZDI-23-352.
An out-of-bounds write is more serious than a read because the attacker can change memory, not only see it. Parsers that write decoded image data into a buffer sized from the file header are a well known source of this class of bug. The record does not flag the CVE in CISA KEV, and ZDI describes a coordinated release on 31 March 2023.
Quick check
Why are there two PNG advisories?
ZDI published them as separate cases, ZDI-23-351 and ZDI-23-352, each with its own CVE. They are likely separate code paths, though the advisories do not say so.
Is a fixed build named?
No. Read the vendor version history for the build.
Sources
Last reviewed: 19 October 2026.