CVE-2025-43550
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.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 confidenceAdobe Acrobat Reader contains a Use After Free vulnerability where memory is accessed after it has been freed, allowing an attacker to execute arbitrary code. The flaw is triggered when a victim opens a specially crafted malicious PDF file, with code execution occurring in the context of the current user.
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>= 15.008.20082, < 25.001.20531>= 15.008.20082, < 25.001.20529>= 15.008.20082, < 25.001.20531>= 15.008.20082, < 25.001.20529>= 20.001.30002, < 20.005.30774>= 24.0.0, < 24.001.30254>= 20.001.30002, < 20.005.30774CVSS 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.
-
Identify the installed Adobe Acrobat product variantOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat (or About Adobe Reader). Alternatively, right-click the application executable in Program Files and select Properties > Details to view the Product Version.Affected if The product is Adobe Acrobat Dc, Adobe Acrobat Reader Dc, Adobe Acrobat, or Adobe Acrobat Reader, and the version falls within the affected ranges.
-
Verify the exact product version numberRecord the full version number displayed in the About dialog or file properties. For Windows, common install paths are: C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe or C:\Program Files\Adobe\Acrobat Reader DC\Reader\AcroRd32.exeAffected if The version is 15.008.20082 or higher but below 25.001.20529 (for DC/Reader DC), below 20.005.30774 (for classic version 20.x), or below 24.001.30254 (for classic version 24.x).
-
Confirm the PDF handling feature is in useThis vulnerability is triggered when opening a PDF file. No special configuration check is needed, as the vulnerable code path is exercised simply by opening any PDF document.Affected if The user opens a PDF file using the affected Adobe Acrobat or Reader version, which is the normal intended use of the software.
If the installed Adobe Acrobat or Reader version matches the affected ranges (15.008.20082 to 25.001.20529 for DC variants, 20.001.30002 to 20.005.30774 or 24.0.0 to 24.001.30254 for classic variants), the environment is vulnerable when opening PDF files.
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.3077424.001.3025425.001.20529
Update Adobe Acrobat Reader to a version newer than 24.001.30235, 20.005.30763, or 25.001.20521. Users should avoid opening untrusted PDF files from unknown sources.
Acrobat DC/Reader DC: 25.001.20531+; Acrobat Classic 2020: 20.005.30774+; Acrobat Classic 2024: 24.001.30254+
- 1. Identify the exact Adobe Acrobat or Acrobat Reader version currently installed by opening the application, clicking Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. For Acrobat/Acrobat Reader DC (Continuous track): Upgrade to version 25.001.20531 or later.
- 3. For Acrobat/Acrobat Reader (Classic - 2020): Upgrade to version 20.005.30774 or later.
- 4. For Acrobat/Acrobat Reader (Classic - 2024): Upgrade to version 24.001.30254 or later.
- 5. Download the appropriate update from the Adobe Acrobat download page at get.adobe.com/reader or get.adobe.com/acrobat.
- 6. Close all instances of Adobe Acrobat/Reader before installing the update.
- 7. Run the installer and follow the prompts to complete the upgrade.
- 8. After installation, verify the new version by checking Help > About to confirm the version number matches the fixed release.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43550 — 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-43550 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