CVE-2025-0906
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 buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-25434.
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 confidenceAn out-of-bounds read vulnerability exists in PDF-XChange Editor's JB2 (JBIG2) file parser due to insufficient validation of user-supplied data. The lack of bounds checking allows reading past the end of an allocated buffer, enabling information disclosure. This can be chained with other vulnerabilities to achieve arbitrary code execution.
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.
-
Confirm PDF-XChange Editor installationCheck for the application in the system: look in Program Files for 'PDF-XChange' folder, check Start Menu shortcuts, or look in Windows Registry under HKLM\SOFTWARE\PDF-XChange or HKCU\SOFTWARE\PDF-XChangeAffected if PDF-XChange Editor is not found on the system, the user is not affected by this CVE
-
Determine installed versionOpen PDF-XChange Editor, go to Help > About, or right-click the executable (PDFXCview.exe or similar) in Program Files and select Properties > Details to view the File VersionAffected if The version number shown is less than 10.4.2.390 (for example, 10.3.x, 9.x, or earlier)
-
Verify JB2/JBIG2 parsing capability is presentAttempt to open a sample JB2 or JBIG2 file (file extension .jb2 or .jbig) in PDF-XChange Editor, or check if the application can render PDF files containing JBIG2 image streamsAffected if The application successfully opens or parses JB2/JBIG2 content - the vulnerable parser code path is reachable
-
Check for update availabilityIn the application, go to Help > Check for Updates, or visit the vendor website manually to compare your version against the fixed release 10.4.2.390Affected if A newer version is available and your current version is below 10.4.2.390
A user is affected if PDF-XChange Editor is installed with a version lower than 10.4.2.390 and the application can process JB2/JBIG2 files or PDF documents containing JBIG2 image data.
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
Restrict opening of untrusted JB2/JBIG2 files until a vendor patch is available; consider disabling JB2 support in PDF-XChange Editor or deploying additional file-type filtering at the network perimeter.
10.4.2.390
- Navigate to the official PDF-XChange Editor website or the vendor's download page
- Download the latest version of PDF-XChange Editor (ensure it is version 10.4.2.390 or later)
- Close any running instances of PDF-XChange Editor
- Install the downloaded update by running the installer
- Restart the application if it does not restart automatically
- Verify the installed version by checking Help > About to confirm version 10.4.2.390 or later is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0906 — 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-0906 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