CVE-2021-35981
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.20054 (and earlier), 2020.004.30005 (and earlier) and 2017.011.30197 (and earlier) are affected by an Use-after-free vulnerability. An unauthenticated attacker could leverage this vulnerability to achieve 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 confidenceA use-after-free vulnerability in Adobe Acrobat Reader DC allows an unauthenticated attacker to achieve arbitrary code execution through a specially crafted PDF file. The vulnerability exploits memory corruption when the victim opens a malicious file, enabling the attacker to execute code in the context of the current user's session.
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, <= 21.005.20054>= 17.011.30059, <= 17.011.30197>= 20.001.30005, <= 20.004.30005>= 15.008.20082, <= 21.005.20054>= 17.011.30059, <= 17.011.30197>= 20.001.30005, <= 20.004.30005CVSS 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.
-
Verify Adobe Acrobat installationCheck if Adobe Acrobat Reader DC or Adobe Acrobat DC is installed. On Windows, look in Program Files or Program Files (x86) for Adobe folders, or check the Windows Registry under HKLM\SOFTWARE\Adobe. On macOS, check /Applications for Adobe Acrobat or Adobe Acrobat Reader.Affected if The software is present on the system.
-
Determine installed version on WindowsRight-click the AcroRd32.exe or AcroPDF.dll file in the installation directory (typically under C:\Program Files\Adobe\Acrobat DC\ or C:\Program Files (x86)\Adobe\Acrobat Reader DC\), select Properties, and view the File Version on the Details tab. Alternatively, run: wmic datafile where "name='C:\\Program Files\\Adobe\\Acrobat DC\\AcroRd32.exe'" get VersionAffected if A version number is retrieved.
-
Determine installed version on macOSRight-click the Adobe Acrobat Reader.app or Adobe Acrobat.app in Applications, select Get Info, and view the Version number. Alternatively, run: defaults read "/Applications/Adobe Acrobat Reader DC.app/Contents/Info" CFBundleVersionAffected if A version number is retrieved.
-
Compare version against affected rangesMatch your installed version number to the following affected ranges: 15.008.20082 through 21.005.20054 (2021 track), 17.011.30059 through 17.011.30197 (2017 track), or 20.001.30005 through 20.004.30005 (2020 track).Affected if The installed version falls within any of these three ranges.
A user is affected if Adobe Acrobat Reader DC or Adobe Acrobat DC is installed with a version matching 15.008.20082-21.005.20054, 17.011.30059-17.011.30197, or 20.001.30005-20.004.30005, as the vulnerability triggers upon opening a 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 a version later than 2021.005.20054 (for 2021 track), 2020.004.30005 (for 2020 track), or 2017.011.30197 (for 2017 track), or apply the relevant vendor security patches.
Upgrade to latest available Adobe Acrobat DC/Reader version (versions greater than 21.005.20054, 20.004.30005, or 17.011.30197 depending on your release track)
- 1. Open Adobe Acrobat DC or Adobe Acrobat Reader DC
- 2. Navigate to Help > Check for Updates or use the built-in update mechanism
- 3. Download and install the latest available version from the official Adobe website at https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- 4. Alternatively, navigate to Help > About Adobe Acrobat DC to verify the installed version
- 5. Ensure the version number is higher than the last vulnerable release for your release track (21.005.20054, 20.004.30005, or 17.011.30197)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35981 — 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-35981 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