CVE-2025-47111
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 a NULL Pointer Dereference vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability to crash the application, causing a disruption in service. 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 · moderate confidenceAdobe Acrobat Reader contains a NULL Pointer Dereference vulnerability that can be triggered when a user opens a specially crafted malicious PDF file. The vulnerability leads to application crash and denial of service.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 the installed Adobe productOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat) to see the exact product name and version number. Alternatively, check Add/Remove Programs (Windows) or Applications folder (Mac).Affected if The product is Adobe Acrobat Reader DC, Adobe Acrobat DC, Adobe Acrobat Reader, or Adobe Acrobat (not the standalone Standard versions, as those are not listed as affected).
-
Determine the exact version numberNote the full version number displayed in the About dialog (for example: 24.001.30253 or 20.005.30760). Compare this against the affected version ranges.Affected if The installed version falls into any of these ranges: < 25.001.20531, < 25.001.20529, >= 20.0 and < 20.005.30774, >= 24.0.0 and < 24.001.30254.
-
Assess PDF handling behaviorDetermine if users in your environment open PDF files from untrusted or unknown sources, such as email attachments from unknown senders, downloaded files from the internet, or files shared via removable media.Affected if Users regularly open PDF files from untrusted sources, as the vulnerability is triggered only when a specially crafted malicious PDF is opened.
A user is affected if they have Adobe Acrobat Reader or Acrobat (DC or classic) installed with a version number that falls within the affected ranges AND they open untrusted 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.3077424.001.3025425.001.20529
Update Adobe Acrobat Reader to the latest version beyond 24.001.30235, 20.005.30763, and 25.001.20521. Avoid opening untrusted PDF files.
Acrobat/Acrobat Reader DC: 25.001.20531 | Acrobat/Acrobat Reader 24.x: 24.001.30254 | Acrobat/Acrobat Reader 20.x: 20.005.30774
- Open Adobe Acrobat or Acrobat Reader
- Navigate to Help > Check for Updates or use the built-in update mechanism
- Download and install the latest version for your product line: For Acrobat/Acrobat Reader DC: version 25.001.20531 or later; For Acrobat/Acrobat Reader 24.x: version 24.001.30254 or later; For Acrobat/Acrobat Reader 20.x: version 20.005.30774 or later
- Restart the application after the update completes
- Verify the installed version matches or exceeds the fixed versions listed above
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47111 — 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-47111 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