CVE-2025-0907
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPDF-XChange Editor JB2 File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of PDF-XChange Editor. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of JB2 files. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated object. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-25435.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePDF-XChange Editor contains an out-of-bounds read vulnerability in its JB2 (JBIG2) file parser. The application fails to properly validate user-supplied data during JB2 image parsing, allowing read operations to extend past the boundaries of allocated memory buffers. This can expose sensitive memory contents and, when combined with other vulnerabilities, enables arbitrary code execution in the current process context.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.4.2.390CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate PDF-XChange Editor installationSearch for the application executable (pdfxcview.exe or PDF-XChange Editor.exe) in common installation directories such as C:\Program Files\Tracker Software\PDF-XChange Editor or C:\Program Files (x86)\Tracker Software\PDF-XChange Editor. Also check the Windows Programs and Features list or use 'wmic product where "name like 'PDF-XChange%'" get name,version'Affected if PDF-XChange Editor is not found on the system, this CVE does not apply.
-
Determine installed version numberRight-click the executable and select Properties, then view the Details tab for the Product Version. Alternatively, open the application and go to Help > About PDF-XChange Editor to display the exact version string.Affected if Version information cannot be retrieved, treat as unknown and follow vendor guidance.
-
Compare version against vulnerability thresholdCompare the installed version to the affected range. The vulnerable version range is any version lower than 10.4.2.390. Example: if installed version is 10.3.1.256 or 10.4.1.381, it falls within the affected range.Affected if Installed version is less than 10.4.2.390 (for example 10.4.2.389, 10.3.0.189, or 9.4.0.356), the application is vulnerable.
-
Assess JB2 file processing exposureDetermine if the application is used to open PDF files that may contain JB2 (JBIG2) embedded images. JB2 is commonly used in scanned document PDFs. There is no explicit enable/disable setting for JB2 parsing in the editor - the vulnerability triggers upon opening a specially crafted PDF containing a JB2 image.Affected if Vulnerable version is in use AND the user opens untrusted or specially crafted PDF files containing JB2 images.
A user is affected if PDF-XChange Editor version is below 10.4.2.390 AND they open PDF files containing JB2 (JBIG2) images from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.4.2.390
Update PDF-XChange Editor to the latest version once the vendor releases a patch. Until then, avoid opening untrusted or suspicious JB2-containing PDF files.
PDF-XChange Editor 10.4.2.390 or later
- Check the current version of PDF-XChange Editor by opening the application and navigating to Help > About or using the About dialog
- Download PDF-XChange Editor version 10.4.2.390 or later from the official vendor website (www.tracker-software.com)
- Close all instances of PDF-XChange Editor
- Run the installer and follow the prompts to upgrade to the fixed version
- Verify the installation was successful by checking Help > About shows version 10.4.2.390 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0907 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0907 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data