dbcve.org
Acrobat DcApplication · Adobe

CVE-2025-43577

HIGH · 7.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 20.005.30774 / 24.001.30254 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Acrobat Reader versions 24.001.30235, 20.005.30763, 25.001.20521 and earlier are affected by a Use After Free vulnerability that could result in arbitrary code execution 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 confidence

Adobe Acrobat Reader contains a Use After Free vulnerability where memory is accessed after it has been freed, allowing an attacker to achieve arbitrary code execution in the context of the current user. Exploitation requires the victim to open a specially crafted malicious PDF file.

MitigationUpdate Adobe Acrobat Reader to the latest version beyond the affected releases (24.001.30235, 20.005.30763, 25.001.20521) to remediate the vulnerability.

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
Acrobat DcApplication
Affected:>= 15.008.20082, < 25.001.20531>= 15.008.20082, < 25.001.20529
Acrobat Reader DcApplication
Affected:>= 15.008.20082, < 25.001.20531>= 15.008.20082, < 25.001.20529
AcrobatApplication
Affected:>= 20.001.30002, < 20.005.30774>= 24.0.0, < 24.001.30254
Acrobat ReaderApplication
Affected:>= 20.001.30002, < 20.005.30774

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Adobe Acrobat Reader installation
    Open Windows Settings > Apps > Apps & features, or on macOS check /Applications folder for 'Adobe Acrobat Reader' or 'Adobe Acrobat Reader DC'
    Affected if Adobe Acrobat Reader or Adobe Acrobat is installed on the system
  2. Retrieve installed version number
    In Windows: Right-click the application in Start menu > Properties > Details tab > Product version. On macOS: Right-click app > Get Info > Version. Alternatively, launch Reader, go to Help > About Adobe Acrobat Reader
    Affected if The version cannot be determined or Reader is not installed
  3. Compare against affected versions for Acrobat Reader DC
    Version format is xx.xxx.xxxxx. Check if version falls in range: 15.008.20082 to 25.001.20530 (continuous range), or 20.001.30002 to 20.005.30773
    Affected if Installed version is 15.008.20082 or higher but below 25.001.20531, OR 20.001.30002 through 20.005.30773
  4. Compare against affected versions for standalone Acrobat Reader
    Check if version is 20.001.30002 through 20.005.30773
    Affected if Installed version is 20.001.30002 or higher but below 20.005.30774
  5. Verify PDF file handling is accessible
    Confirm that PDF files can be opened in the installed Adobe Reader application
    Affected if User can open PDF files in Adobe Reader (the vulnerability is triggered upon opening a malicious PDF)

If Adobe Acrobat Reader or Adobe Acrobat is installed with a version between 15.008.20082 and 25.001.20530 (for DC versions), or between 20.001.30002 and 20.005.30773 (for standalone Reader), the environment is affected and the vulnerability can be triggered by opening a malicious PDF file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 20.005.30774 / 24.001.30254 / 25.001.20529 or later
Fixed in 20.005.3077424.001.3025425.001.20529
Interim mitigation

Update Adobe Acrobat Reader to the latest version beyond the affected releases (24.001.30235, 20.005.30763, 25.001.20521) to remediate the vulnerability.

Recommended fix High confidence

Acrobat Dc/Reader Dc: 25.001.20531 or later; Acrobat/Reader 20.x: 20.005.30774 or later; Acrobat/Reader 24.x: 24.001.30254 or later

  1. 1. Verify the current installed version of Adobe Acrobat or Acrobat Reader by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
  2. 2. Identify the product line (Acrobat Dc, Acrobat Reader Dc, Acrobat, or Acrobat Reader) and your specific version number from the About dialog.
  3. 3. For Acrobat Dc/Acrobat Reader Dc: If your version is below 25.001.20531, upgrade to version 25.001.20531 or later.
  4. 4. For Acrobat/Acrobat Reader: If you are on version 20.x (20.001.30002 through 20.005.30773), upgrade to version 20.005.30774 or later.
  5. 5. For Acrobat/Acrobat Reader: If you are on version 24.x (24.0.0 through 24.001.30253), upgrade to version 24.001.30254 or later.
  6. 6. Download the appropriate fixed version from the official Adobe website at helpx.adobe.com or through your organization's software distribution channels.
  7. 7. Close all running instances of Adobe Acrobat/Reader before installing the update.
  8. 8. Run the installer and follow the prompts to complete the upgrade.
Caveat Standard Adobe Acrobat updates typically preserve user settings and preferences; however, test critical workflows in a staging environment before deploying enterprise-wide to ensure compatibility with existing workflows and integrations.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43577 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43577 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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