CVE-2021-28551
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.20155 (and earlier), 2020.001.30025 (and earlier) and 2017.011.30196 (and earlier) are affected by an Out-of-bounds read 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 · moderate confidenceThis is an out-of-bounds read vulnerability in Adobe Acrobat Reader DC that allows an unauthenticated attacker to achieve arbitrary code execution in the context of the current user. Exploitation requires the victim to open a malicious PDF file, making this a client-side attack vector.
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.20149>= 15.008.20082, <= 21.001.20150>= 15.008.20082, <= 21.001.20149>= 17.011.30180, <= 17.011.30194>= 20.001.30005, <= 20.001.30020>= 17.011.30180, <= 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
- 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 installed Adobe productOpen Adobe Acrobat Reader or Acrobat, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat) to view the exact version number. Alternatively, check Add/Remove Programs (Windows) or Applications folder (Mac).Affected if The installed product is Adobe Acrobat DC, Adobe Acrobat Reader DC, Adobe Acrobat, or Adobe Acrobat Reader
-
Confirm version for Acrobat Reader DC or Acrobat DCLook for the version in the format 21.x.x.xxxxx or 15.x.x.xxxxx in the About dialog. Record the full version number including the last five digits.Affected if The version is between 15.008.20082 and 21.001.20150 inclusive, or between 15.008.20082 and 21.001.20149 inclusive (check both ranges)
-
Confirm version for Acrobat or Acrobat Reader (classic)Look for the version in the format 17.x.xxxxxx or 20.x.xxxxx in the About dialog. Record the full version number.Affected if The version is between 17.011.30180 and 17.011.30194 inclusive, or between 20.001.30005 and 20.001.30020 inclusive (check both ranges)
-
Verify PDF handling exposureThis vulnerability is triggered when a user opens a malicious PDF file. Check whether the system routinely opens PDF files from untrusted sources or email attachments.Affected if Users in the environment open PDF files from external or untrusted sources without verification
You are affected if Adobe Acrobat or Acrobat Reader is installed with a version matching the affected ranges: 15.008.20082 to 21.001.20150, 17.011.30180 to 17.011.30194, or 20.001.30005 to 20.001.30020.
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 patched version beyond 2021.001.20155, 2020.001.30025, or 2017.011.30196. Additionally, train users to avoid opening untrusted or unexpected PDF attachments.
Acrobat/Reader 2021.x → 2021.001.20156+ | 2020.x → 2020.001.30026+ | 2017.x → 2017.011.30197+
- 1. Identify the current Adobe Acrobat/Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat)
- 2. For 2021.x track users: Upgrade to version 2021.001.20156 or later
- 3. For 2020.x track users: Upgrade to version 2020.001.30026 or later
- 4. For 2017.x track users: Upgrade to version 2017.011.30197 or later
- 5. Download the appropriate updated version from the official Adobe website or use the application's built-in update feature (Help > Check for Updates)
- 6. Install the update and restart the application
- 7. Verify the installed version matches or exceeds the fixed release for your track
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-2021-28551 — 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-28551 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