CVE-2021-39845
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 DC versions 2021.005.20060 (and earlier), 2020.004.30006 (and earlier) and 2017.011.30199 (and earlier) are affected by a stack overflow vulnerability due to insecure handling of a crafted PDF file, potentially resulting in memory corruption in the context of the current user. Exploitation requires user interaction in that a victim must open a crafted PDF file in Acrobat Reader.
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 confidenceStack overflow vulnerability in Adobe Acrobat Reader DC when processing maliciously crafted PDF files, leading to memory corruption in the current user's context. Exploitation requires the victim to open a specially crafted PDF file.
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>= 20.001.30005, <= 20.004.30006>= 17.011.30059, <= 17.011.30199>= 20.001.30005, <= 20.004.30006>= 17.011.30059, <= 17.011.30199>= 15.008.20082, <= 21.005.20058>= 15.008.20082, <= 21.005.20060>= 15.008.20082, <= 21.005.20058>= 15.008.20082, <= 21.005.20060CVSS 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
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/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 productOpen Adobe Acrobat Reader or Acrobat, then go to Help > About Adobe Acrobat Reader (or Acrobat) to see the exact product name and version number displayed in the dialog windowAffected if The product is Adobe Acrobat, Adobe Acrobat Reader, Adobe Acrobat DC, or Adobe Acrobat Reader DC
-
Note the exact version numberRecord the full version number shown in the About dialog (for example: 20.004.30006 or 21.005.20058)Affected if Version cannot be determined or is not visible
-
Compare against affected version rangesCheck if your version falls within any of these ranges: Acrobat/Acrobat Reader 20.001.30005 to 20.004.30006, 17.011.30059 to 17.011.30199; Acrobat DC/Reader DC 15.008.20082 to 21.005.20058 (Classic) or 15.008.20082 to 21.005.20060 (Continuous)Affected if Installed version is greater than or equal to 20.001.30005 and less than or equal to 20.004.30006, OR greater than or equal to 17.011.30059 and less than or equal to 17.011.30199, OR greater than or equal to 15.008.20082 and less than or equal to 21.005.20058 (for some DC variants) or 21.005.20060 (
-
Determine the product trackCheck whether the installation is the Classic (15.x-20.x) or Continuous (21.x) track by looking at the version number format - Classic versions are in the 15.x-20.x range while Continuous versions are 21.xAffected if Using the Classic track version 15.x-20.x or Continuous track version 21.x within the affected ranges
A user is affected if Adobe Acrobat or Acrobat Reader DC/Classic is installed with a version number matching any of the documented affected ranges and the user opens a specially crafted malicious PDF file.
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 · scopedUpdate Adobe Acrobat Reader DC to the latest version and exercise caution when opening PDF files from untrusted sources.
Acrobat/Acrobat Reader DC 2021.006.20080+, 2020.005.30018+, or 2017.012.30233+ (depending on your product track)
- Identify the installed Adobe Acrobat or Acrobat Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat)
- For version 2021.x (2021.005.20060 and earlier): Upgrade to version 2021.006.20080 or later
- For version 2020.x (2020.004.30006 and earlier): Upgrade to version 2020.005.30018 or later
- For version 2017.x (2017.011.30199 and earlier): Upgrade to version 2017.012.30233 or later
- Download the latest version from helpx.adobe.com or use the built-in Help > Check for Updates functionality
- Restart the application after installation
- Verify the installed version reflects the patched release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-39845 — 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-2021-39845 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