dbcve.org
Acrobat DcApplication · Adobe

CVE-2025-43578

MEDIUM · 5.5 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 →
58/100
Remediation priority · Elevated
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 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 confidence

Adobe Acrobat Reader contains an out-of-bounds read vulnerability allowing disclosure of sensitive memory contents. This information disclosure can be leveraged to defeat ASLR (Address Space Layout Randomization) as a secondary attack step. Exploitation requires a victim to open a specially crafted malicious PDF file.

MitigationUpdate Adobe Acrobat Reader to a version later than 24.001.30235, 20.005.30763, or 25.001.20521. Avoid opening untrusted PDF files from unknown sources.

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

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

  1. Verify Adobe Acrobat or Reader is installed
    On Windows, check Start menu for Adobe Acrobat/Reader entries, or check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe for Acrobat or Reader. On macOS, check /Applications for Adobe Acrobat or Adobe Reader.
    Affected if Adobe Acrobat or Adobe Acrobat Reader is not found on the system, the vulnerability does not apply.
  2. Determine the installed version number
    Open Adobe Acrobat/Reader, then go to Help > About (or on Windows, right-click the executable and select Properties > Details to view Product Version).
    Affected if The version cannot be determined, skip to next checks.
  3. Compare version against affected ranges for Acrobat/Reader DC
    For Continuous track versions (15.x): note that versions 15.008.20082 through 25.001.20528 (or 25.001.20530 for some tracks) are affected. Compare your installed 15.x or 25.x version number to these bounds.
    Affected if Installed version falls within 15.008.20082 <= version < 25.001.20529 or < 25.001.20531.
  4. Compare version against affected ranges for Acrobat/Reader Classic
    For Classic track versions (20.x and 24.x): versions 20.001.30002 through 20.005.30773 are affected, as are versions 24.0.0 through 24.001.30253. Compare your installed 20.x or 24.x version.
    Affected if Installed version falls within 20.001.30002 <= version < 20.005.30774 OR 24.0.0 <= version < 24.001.30254.
  5. Confirm the attack vector condition
    This vulnerability is triggered only when a user opens a specially crafted malicious PDF file. Review your organization's policy on opening PDF files from untrusted or unknown sources.
    Affected if Users routinely open PDF files from untrusted sources, increasing the likelihood of exploitation if a vulnerable version is installed.

If Adobe Acrobat or Reader is installed and the version falls within any of the affected ranges (15.008.20082 to 25.001.20528/30, 20.001.30002 to 20.005.30773, or 24.0.0 to 24.001.30253), the environment is potentially affected.

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 a version later than 24.001.30235, 20.005.30763, or 25.001.20521. Avoid opening untrusted PDF files from unknown sources.

Recommended fix High confidence

Adobe Acrobat DC/Reader DC: 25.001.20531+ | Adobe Acrobat/Reader Classic 2020: 20.005.30774+ | Adobe Acrobat/Reader Classic 2024: 24.001.30254+

  1. 1. Identify which Adobe Acrobat product and track you are using (Continuous vs. Classic)
  2. 2. For Adobe Acrobat DC / Acrobat Reader DC (Continuous track): Upgrade to version 25.001.20531 or later
  3. 3. For Adobe Acrobat / Acrobat Reader Classic 2020: Upgrade to version 20.005.30774 or later
  4. 4. For Adobe Acrobat / Acrobat Reader Classic 2024: Upgrade to version 24.001.30254 or later
  5. 5. Download the updated version from the official Adobe website or use the Adobe Creative Cloud desktop app to update
  6. 6. Verify the installed version after update: Open Acrobat/Reader, go to Help > About Adobe Acrobat/Reader to confirm the version number
  7. 7. Ensure users are warned not to open untrusted or unexpected PDF files, as exploitation requires user interaction (opening a malicious file)
Caveat Security patches typically have no functional breaking changes; ensure existing PDF workflows are tested after upgrade

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
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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