dbcve.org
Acrobat DcApplication · Adobe

CVE-2025-43579

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 Information Exposure vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to gain unauthorized access to sensitive information. Exploitation of this issue does not require user interaction.

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 · moderate confidence

This is an information exposure vulnerability in Adobe Acrobat Reader that allows security feature bypass, potentially enabling unauthorized access to sensitive data. The vulnerability affects versions 24.001.30235, 20.005.30763, 25.001.20521 and earlier, and exploitation does not require user interaction.

MitigationApply the latest security update for Adobe Acrobat Reader from the vendor's official channels to address the security feature bypass.

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. Identify installed Adobe product
    Check for presence of Adobe Acrobat or Acrobat Reader. On Windows, typical paths include C:\Program Files\Adobe\Acrobat DC\, C:\Program Files (x86)\Adobe\Acrobat Reader DC\, or C:\Program Files\Adobe\Acrobat 2024\. On macOS, check /Applications/ for Adobe Acrobat or Adobe Acrobat Reader.
    Affected if Any version of Adobe Acrobat or Acrobat Reader is installed
  2. Retrieve installed version number
    Windows: Right-click the executable (Acrobat.exe or AcroRd32.exe), select Properties, and view the File Version on the Details tab. Alternatively, run 'Get-ItemProperty -Path "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" | Select-Object VersionInfo' in PowerShell. macOS: Right-click the app in Applications, select Get Info, and note the version shown.
    Affected if Version cannot be determined or differs from what is displayed in the application
  3. Compare version against affected ranges
    Compare your installed version to these vulnerable ranges: Acrobat DC/Reader DC: >= 15.008.20082 and < 25.001.20531 (or < 25.001.20529 depending on update track); Acrobat/Reader (classic): >= 20.001.30002 and < 20.005.30774, or >= 24.0.0 and < 24.001.30254
    Affected if Installed version falls within any of the affected ranges (15.008.20082 to 25.001.20530 for DC products, or 20.001.30002 to 20.005.30773 or 24.0.0 to 24.001.30253 for classic products)

If Adobe Acrobat or Acrobat Reader is installed and the version falls within the affected ranges (15.008.20082 to 25.001.20530/25.001.20528 for DC, or 20.001.30002 to 20.005.30773/24.001.30253 for classic), the environment is affected by this security feature bypass vulnerability.

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

Apply the latest security update for Adobe Acrobat Reader from the vendor's official channels to address the security feature bypass.

Recommended fix High confidence

Acrobat DC/Reader DC: 25.001.20531 or later; Acrobat/Reader classic 24.x: 24.001.30254 or later; Acrobat/Reader classic 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 Adobe Acrobat Reader (or About Adobe Acrobat).
  2. 2. Determine the product line (Acrobat DC/Reader DC continuous track vs. Acrobat/Reader classic track) based on the version number.
  3. 3. For Acrobat/Reader DC (continuous track): Upgrade to version 25.001.20531 or later.
  4. 4. For Acrobat/Reader classic track (version 20.x): Upgrade to version 20.005.30774 or later.
  5. 5. For Acrobat/Reader classic track (version 24.x): Upgrade to version 24.001.30254 or later.
  6. 6. Verify the upgrade was successful by checking Help > About again to confirm the version meets or exceeds the minimum fixed version for your track.
  7. 7. Ensure the updated software is deployed organization-wide using your standard software distribution method (e.g., SCCM, Group Policy, or enterprise patch management).
Caveat Standard Adobe update - minimal risk; ensure compatibility with existing PDF workflows and integrations before broad deployment

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-43579 — 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-43579 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