CVE-2021-28560
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 versions 2021.001.20150 (and earlier), 2020.001.30020 (and earlier) and 2017.011.30194 (and earlier) are affected by a Heap-based Buffer Overflow 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 confidenceHeap-based buffer overflow vulnerability in Adobe Acrobat Reader DC allows remote code execution via malicious PDF file. When a victim opens the specially crafted PDF, the overflow corrupts heap memory enabling attacker-controlled code execution in the current user's context.
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.001.20150>= 15.008.20082, <= 21.001.20150>= 17.011.30059, <= 17.011.30194>= 20.001.30005, <= 20.001.30020>= 17.011.30059, <= 17.011.30194>= 20.001.30005, <= 20.001.30020CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 installed Adobe productCheck installed programs in Windows Control Panel > Programs and Features, or review the program's Help > About menu. Look for Adobe Acrobat DC, Adobe Acrobat Reader DC, Adobe Acrobat, or Adobe Acrobat Reader.Affected if The product name contains Adobe Acrobat (DC or classic) or Adobe Acrobat Reader.
-
Determine the exact version numberFor Adobe Acrobat/Reader DC: Open the application, go to Help > About Adobe Acrobat/Reader DC, and note the version displayed (format: YYMM.xxxxxx, for example 21.001.20150). For classic Adobe Acrobat/Reader: Check Help > About Adobe Acrobat/Reader for version like 17.011.30194.Affected if A version number is displayed in the About dialog.
-
Compare version against affected rangesMatch your installed version to the affected ranges: For DC products: versions 15.008.20082 through 21.001.20150. For classic products: versions 17.011.30059 through 17.011.30194, OR versions 20.001.30005 through 20.001.30020.Affected if Your installed version falls within any of these ranges.
-
Verify the application can open PDF filesConfirm the installed product has PDF rendering capabilities enabled. Check if the application can open and display PDF documents.Affected if The product is a full Acrobat/Reader variant (not a limited trial or disabled version) and can process PDF files.
You are affected if Adobe Acrobat or Adobe Acrobat Reader is installed with a version between 15.008.20082 and 21.001.20150 (DC), between 17.011.30059 and 17.011.30194, or between 20.001.30005 and 20.001.30020 (classic), and the application can open 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 · scopedUpdate Adobe Acrobat Reader DC to version 2021.001.20155 (or later for 2021 track), 2021.001.30025 (or later for 2020 track), or 2017.011.30196 (or later for 2017 track). Supplement with user training to avoid opening untrusted PDF attachments.
Acrobat DC 2021.001.20155 or later; Acrobat Reader DC 2021.001.20155 or later; Acrobat 2020.001.30025 or later; Acrobat Reader 2020.001.30025 or later; Acrobat 2017.011.30215 or later; Acrobat Reader 2017.011.30215 or later
- Open Adobe Acrobat or Acrobat Reader
- Navigate to Help > Check for Updates or use the Help menu
- Allow the application to check for and install the latest updates
- Alternatively, download the latest version from the official Adobe website: https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- Restart the application after updates complete
- Verify the version by going to Help > About Adobe Acrobat/Reader
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28560 — 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-28560 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