CVE-2025-9326
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 · uneditedFoxit PDF Reader PRC File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PDF Reader. 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 PRC 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 vulnerability to execute code in the context of the current process. Was ZDI-CAN-26784.
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 in Foxit PDF Reader's PRC file parser allows remote code execution by reading past the end of an allocated buffer due to insufficient validation of user-supplied data during PRC file parsing.
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<= 13.1.7.23637>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.4.1.27687= 2025.1.0.27937<= 13.1.7.63027>= 2023.1.0.55583, <= 2023.3.0.63083>= 2024.1.0.63682, <= 2024.4.1.66479= 2025.1.0.66692< 2025.1.0.27937<= 2025.1.0.66692CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/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 Foxit PDF Reader installationCheck for Foxit PDF Reader in program directories (C:\Program Files\Foxit or C:\Program Files (x86)\Foxit), Start Menu, or desktop shortcuts. Also check Windows Programs and Features list.Affected if Foxit PDF Reader is installed on the system
-
Identify installed Foxit PDF Reader versionRight-click the Foxit PDF Reader executable (e.g., FoxitReader.exe) → Properties → Details tab → Product Version. Or launch the application → Help → About Foxit Reader.Affected if Version is lower than 2025.1.0.27937, or version is 2025.1.0.66692 or lower (specific to the 13.x legacy versioning branch)
-
Verify PRC file handling capabilityCheck if the application can open .PRC files by attempting to open a PRC file or verifying .PRC file association in Windows Default Apps settings.Affected if PRC file type is associated with Foxit PDF Reader and functional
User is affected if Foxit PDF Reader is installed with a version that falls within the affected ranges AND the application is capable of opening or parsing PRC files.
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 · scoped2025.1.0.27937
Apply vendor patch from Foxit to update PDF Reader to a patched version, or disable opening of PRC files in untrusted documents until the update is applied.
Foxit PDF Reader/PDF Editor version 2025.1.0.27938 or later (latest available version)
- 1. Visit the official Foxit software download page at www.foxit.com to obtain the latest version
- 2. Download the current version of Foxit PDF Reader or PDF Editor
- 3. Uninstall the current Foxit PDF software from your system
- 4. Install the latest available version of Foxit PDF Reader or PDF Editor
- 5. Verify the installed version matches or exceeds the fixed release (2025.1.0.27938 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9326 — 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-9326 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