CVE-2025-27161
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 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 crafted files, allowing an attacker to read past the end of allocated memory structures. Successful exploitation could enable code execution in the context of the current user, but requires victim interaction (opening 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.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
- 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.
-
Locate Adobe Acrobat Reader installationCheck for acrord32.exe (32-bit) or acrord64.exe (64-bit) in typical locations: C:\Program Files\Adobe\Acrobat Reader <version>\ or C:\Program Files (x86)\Adobe\Acrobat Reader <version>\Affected if Adobe Acrobat Reader is installed on the system
-
Determine installed version numberRight-click the Acrobat Reader executable, select Properties, and view the Details tab for the Product Version field. Alternatively, open Adobe Acrobat Reader and navigate to Help > About Adobe Acrobat Reader to display the exact version number.Affected if The displayed version falls within any of these ranges: 20.001.30002 through 20.005.30762, 24.0.0 through 24.001.30234, or 15.008.20082 through 25.001.20431
-
Verify product variantConfirm whether the installation is standard Adobe Acrobat Reader or Adobe Acrobat Reader DC by checking the installation folder name and the executable filename (acrord32.exe/acrord64.exe vs Reader/ folder naming)Affected if The product is Adobe Acrobat Reader or Adobe Acrobat Reader Dc with a version matching the affected ranges above
A user is affected if Adobe Acrobat Reader (or Reader Dc) is installed with a version matching >= 20.001.30002 but < 20.005.30763, >= 24.0.0 but < 24.001.30235, or >= 15.008.20082 but < 25.001.20432.
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 version 24.001.30226 or later for the 24.x branch, 20.005.30749 or later for the 20.x branch, or 25.001.20429 or later for the 25.x branch. Users should avoid opening untrusted PDF files.
Adobe Acrobat/Reader 20.005.30763+, 24.001.30235+, or 25.001.20432+ (latest version recommended)
- 1. Open Adobe Acrobat or Adobe Acrobat Reader on your system
- 2. Navigate to Help > Check for Updates (or Help > About Adobe Acrobat Reader)
- 3. Allow the application to check for available updates
- 4. If updates are available, download and install the latest version
- 5. Alternatively, manually download the latest version from the official Adobe website: https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- 6. Restart the application after installation
- 7. Verify the installed version matches or exceeds the fixed version: 20.005.30763 (for version 20.x), 24.001.30235 (for version 24.x), or 25.001.20432 (for version 25.x)
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-27161 — 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-27161 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