CVE-2025-47112
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.30235, 20.005.30763, 25.001.20521 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 that allows reading memory beyond allocated boundaries. This can expose sensitive memory contents including memory addresses, potentially enabling bypass of ASLR. Exploitation requires a victim to 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< 25.001.20531< 25.001.20529< 25.001.20531< 25.001.20529>= 20.0, < 20.005.30774>= 24.0.0, < 24.001.30254>= 20.0, < 20.005.30774CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Verify Adobe Acrobat or Reader is installedCheck the installed programs list in Windows Control Panel, or use the command 'wmic product get name,version' or check the Help > About menu in the applicationAffected if Adobe Acrobat or Adobe Acrobat Reader is present on the system
-
Determine the installed version numberOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat (or Reader) to display the exact version numberAffected if The displayed version falls within any of the affected ranges: 20.0 to 20.005.30773, 24.0.0 to 24.001.30253, or any version below 25.001.20529 (or 25.001.20531 depending on update track)
-
Compare installed version to affected rangesNote the full version string (for example, 24.001.30235 or 20.005.30763) and verify whether it is less than the fixed versions: 20.005.30774, 24.001.30254, or 25.001.20529 (or 25.001.20531)Affected if The installed version is lower than the fixed versions listed in the affected products ranges
-
Identify the update channel or trackCheck if the installation is from the Continuous track (DC) or the Classic track by examining the version number format - Continuous versions use format like 25.001.xxxxx while Classic uses formats like 20.005.xxxxx or 24.001.xxxxxAffected if The version matches the Continuous or Classic track patterns and falls below the fixed version for that specific track
The system is affected if Adobe Acrobat or Reader is installed with a version number that falls below 20.005.30774 (Classic 20.x), 24.001.30254 (Classic 24.x), or 25.001.20529/20531 (Continuous), and the user might open PDF files 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 · scoped20.005.3077424.001.3025425.001.20529
Update Adobe Acrobat Reader to a version newer than 24.001.30235, 20.005.30763, or 25.001.20521. Advise users to avoid opening PDF files from untrusted sources.
Adobe Acrobat/Reader DC: 25.001.20531+ | Acrobat/Reader 2024: 24.001.30254+ | Acrobat/Reader 2020: 20.005.30774+
- 1. Identify the installed Adobe Acrobat or Acrobat Reader version from the Help > About menu
- 2. For Adobe Acrobat/Reader DC (continuous track): upgrade to version 25.001.20531 or later
- 3. For Adobe Acrobat/Reader 2024 (classic track): upgrade to version 24.001.30254 or later
- 4. For Adobe Acrobat/Reader 2020 (classic track): upgrade to version 20.005.30774 or later
- 5. Download the appropriate fixed version from the official Adobe website at get.adobe.com/reader or get.adobe.com/acrobat
- 6. Install the update and restart the application
- 7. Verify the installed version matches or exceeds the fixed version for your track
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47112 — 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-47112 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