dbcve.org
Acrobat DcApplication · Adobe

CVE-2025-43575

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 an out-of-bounds write 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

Out-of-bounds write vulnerability in Adobe Acrobat Reader allows arbitrary code execution when a victim opens a specially crafted malicious PDF file. The vulnerability exists in multiple older versions (20.x, 24.x, 25.x and earlier) of the software.

MitigationUpdate Adobe Acrobat Reader to the latest patched version released by Adobe to address this 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 or Reader installation
    Check for the presence of Adobe Acrobat or Adobe Acrobat Reader on the system. On Windows, look in Program Files for Adobe folder or check the Windows Registry under HKLM\SOFTWARE\Adobe. On macOS, check /Applications for Adobe Acrobat.app or Adobe Acrobat Reader.app.
    Affected if Adobe Acrobat or Adobe Acrobat Reader is installed on the system
  2. Determine exact installed version number
    Open Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat (or About Adobe Acrobat Reader) to display the exact version number. Alternatively, on Windows, check the Windows Registry key HKLM\SOFTWARE\Adobe\Adobe Acrobat\[Version] for the version value, or on macOS right-click the application in Applications and select Get Info to view the version.
    Affected if A version number is retrieved from the installed product
  3. Compare against affected version ranges for Adobe Acrobat Dc / Reader Dc
    Compare your installed version to these vulnerable ranges: versions 15.008.20082 through 25.001.20530 (first range), and versions 15.008.20082 through 25.001.20528 (second range). On Windows, you can also run the application with the command line argument -version to display the version number for comparison.
    Affected if The installed version falls within >= 15.008.20082 and < 25.001.20531, or >= 15.008.20082 and < 25.001.20529
  4. Compare against affected version ranges for Adobe Acrobat / Reader (classic)
    Compare your installed version to these vulnerable ranges: versions 20.001.30002 through 20.005.30773 (classic 20.x), and versions 24.0.0 through 24.001.30253 (24.x). Access the version via Help > About as described in step 2.
    Affected if The installed version falls within >= 20.001.30002 and < 20.005.30774, or >= 24.0.0 and < 24.001.30254

If the installed Adobe Acrobat or Reader version falls within any of the specified vulnerable ranges (15.008.20082 to 25.001.20530/25.001.20528, 20.001.30002 to 20.005.30773, or 24.0.0 to 24.001.30253), the environment is affected by this vulnerability when processing untrusted PDF files.

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 patched version released by Adobe to address this vulnerability.

Recommended fix High confidence

Minimum fixed versions: Acrobat/Acrobat Reader 25.x → 25.001.20531 or later; 24.x → 24.001.30254 or later; 20.x → 20.005.30774 or later

  1. 1. Identify the currently installed Adobe Acrobat or Adobe Acrobat Reader version by opening the application and navigating to Help > About (or Help > About Adobe Acrobat/Reader)
  2. 2. Determine which version branch your installation belongs to (25.x, 24.x, or 20.x) based on the version number
  3. 3. For Acrobat DC / Acrobat Reader DC users: Upgrade to version 25.001.20531 or later
  4. 4. For Acrobat / Acrobat Reader 24.x users: Upgrade to version 24.001.30254 or later
  5. 5. For Acrobat / Acrobat Reader 20.x users: Upgrade to version 20.005.30774 or later
  6. 6. Download the appropriate fixed version from the official Adobe website (helpx.adobe.com) or use your organization's software distribution tool
  7. 7. Close all Adobe applications before running the installer
  8. 8. Run the installer with appropriate administrative privileges
Caveat Standard Adobe security patch with minimal expected breaking changes; may include compatibility adjustments for older PDF features or workflows

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

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43575 — 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-43575 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