CVE-2025-27163
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.30225, 20.005.30748, 25.001.20428 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 disclosure of sensitive memory contents. This information disclosure can be leveraged to defeat Address Space Layout Randomization (ASLR), a critical memory protection mitigation. Exploitation requires a victim to open a specially crafted 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.30002, < 20.005.30763>= 24.0.0, < 24.001.30235>= 15.008.20082, < 25.001.20432>= 20.001.30002, < 20.005.30763>= 15.008.20082, < 25.001.20432CVSS 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.
-
Identify installed Adobe productOpen Adobe Acrobat Reader or Adobe Acrobat, then go to Help > About (or on Windows: Help > About Adobe Acrobat Reader). On Windows, you can also check Add or Remove Programs for the version entry.Affected if The product name shows as Adobe Acrobat Reader, Adobe Acrobat, Adobe Acrobat Reader Dc, or Adobe Acrobat Dc.
-
Record the full version numberNote the exact version number displayed in the About dialog. It typically appears as four digit groups (e.g., 24.001.30235).Affected if A version number is displayed that falls within any of the affected ranges.
-
Compare against affected versionsCheck if your version falls into any of these ranges: Acrobat/Reader 20.x before 20.005.30763; Acrobat/Reader 24.x before 24.001.30235; Acrobat Dc/Reader Dc 15.x-25.x before 25.001.20432. Versions below 20.001.30002 are not affected by this specific CVE.Affected if The installed version is >= 20.001.30002 AND < 20.005.30763, OR >= 24.0.0 AND < 24.001.30235, OR >= 15.008.20082 AND < 25.001.20432.
-
Confirm product variantDetermine if you are running Standard (Acrobat/Reader) or DC variant. DC versions show 'Dc' in the product name. This matters because DC versions have a different version numbering scheme.Affected if Running any DC variant with version < 25.001.20432 is affected.
You are affected if Adobe Acrobat Reader or Adobe Acrobat is installed with a version matching the affected ranges for your product variant, and users 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.3076324.001.3023525.001.20432
Update Adobe Acrobat Reader to a version newer than 24.001.30225, 20.005.30748, or 25.001.20428 as appropriate for the deployment. Implement user awareness training to avoid opening untrusted PDF files.
Adobe Acrobat/Reader 20.005.30763 (Classic track), 24.001.30235 (Continuous track), or 25.001.20432 (Dc track) depending on your product line
- Identify the currently installed Adobe Acrobat or Adobe Acrobat Reader version by opening the application and navigating to Help > About Adobe Acrobat (or Reader)
- For Adobe Acrobat/Reader Classic (20.x line): Upgrade to version 20.005.30763 or later
- For Adobe Acrobat/Reader (24.x line): Upgrade to version 24.001.30235 or later
- For Adobe Acrobat Dc/Acrobat Reader Dc (25.x line): Upgrade to version 25.001.20432 or later
- Download the appropriate fixed version from the official Adobe website at helpx.adobe.com
- Close all Adobe applications before installing the update
- Run the downloaded installer and follow the prompts to complete the installation
- After installation, verify the updated version by checking Help > About again
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-27163 — 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-27163 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