CVE-2025-64899
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 · uneditedAcrobat Reader versions 24.001.30264, 20.005.30793, 25.001.20982, 24.001.30273, 20.005.30803 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
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 confidenceAdobe Acrobat Reader contains an out-of-bounds read vulnerability when parsing specially crafted files. The vulnerability allows reading past the end of an allocated memory structure, which could be leveraged to execute code in the context of the current user. Exploitation requires user interaction—specifically, a victim must open a malicious PDF file.
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>= 20.001.3005, < 20.005.30838>= 24.001.20604, < 24.001.30307>= 24.001.20604, < 24.001.30308< 25.001.20997>= 20.001.3005, < 20.005.30838< 25.001.20997CVSS 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.1/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.
-
Identify installed Adobe productOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat Reader (or similar menu item) to display the version number. Alternatively, right-click the Adobe PDF shortcut and select Properties to view version info.Affected if The product is Adobe Acrobat or Adobe Acrobat Reader (any variant)
-
Determine product variantCheck whether the installed product is Adobe Acrobat (full) or Adobe Acrobat Reader, and whether it includes 'Dc' (Continuous) in the name. This matters because different version ranges apply to each variant.Affected if Product is Adobe Acrobat Reader without 'Dc' variant
-
Check version number against affected rangesLocate the full version string (for example, 20.001.3005 or 24.001.20604) and compare against these ranges: Acrobat/Reader (non-DC): >= 20.001.3005 AND < 20.005.30838, OR >= 24.001.20604 AND < 24.001.30307; Acrobat Dc/Reader Dc: any version < 25.001.20997Affected if Installed version falls within any of the affected ranges listed for the specific product variant
-
Confirm vulnerability trigger conditionThe vulnerability is triggered when a user opens a specially crafted malicious PDF file. There is no server-side or configuration-based check; the flaw exists in the parsing logic for certain PDF structures.Affected if Users open untrusted PDF files from unknown or unverified sources using the affected software version
A user is affected if they run Adobe Acrobat Reader (or Acrobat) in any variant at a version that falls within the vulnerable ranges AND they open potentially malicious PDF 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 · scoped20.005.3083824.001.3030724.001.30308
Update Adobe Acrobat Reader to the latest patched version. Until patched, avoid opening untrusted or unsolicited PDF files from unknown sources.
Upgrade to Acrobat/Reader 20.005.30838 (for v20.x), 24.001.30308 (for v24.x), or 25.001.20997 (for v25.x) or later
- 1. Identify the installed Adobe Acrobat or Reader version by opening the application, clicking Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. Close all Adobe applications completely before proceeding with the update.
- 3. Open Adobe Acrobat Reader or Acrobat and navigate to Help > Check for Updates to automatically download and install the latest version.
- 4. Alternatively, download the appropriate fixed version directly from Adobe's official website: get.adobe.com/reader for Reader or get.adobe.com/acrobat for Acrobat.
- 5. For version 20.x users: Upgrade to version 20.005.30838 or later.
- 6. For version 24.x users: Upgrade to version 24.001.30308 or later.
- 7. For version 25.x users: Upgrade to version 25.001.20997 or later.
- 8. After installation, verify the version by checking Help > About to confirm the fix is applied.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.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 $3,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64899 — 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-64899 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