CVE-2021-28546
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 2020.013.20074 (and earlier), 2020.001.30018 (and earlier) and 2017.011.30188 (and earlier) are missing support for an integrity check. An unauthenticated attacker could leverage this vulnerability to modify content in a certified PDF without invalidating the certification. Exploitation of this issue requires user interaction in that a victim must open the tampered 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 confidenceThis vulnerability in Adobe Acrobat Reader DC allows modification of certified PDF content without invalidating the digital signature. The missing integrity check means attackers can tamper with certified documents while the signature still appears valid, bypassing security controls designed to detect document modification.
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>= 17.011.30059, <= 17.011.30188>= 20.001.30005, <= 20.001.30018>= 15.008.20082, <= 20.013.20074>= 17.011.30059, <= 17.011.30188>= 20.001.30005, <= 20.001.30018>= 15.008.20082, <= 20.013.20074CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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.
-
Locate Adobe Acrobat or Reader installationOpen the application, go to Help > About Adobe Acrobat Reader (or Adobe Acrobat). Alternatively, locate the executable (AcroRd32.exe or AcroTray.exe) in the program files directory and right-click to view Properties > Details for the version number.Affected if The software is Adobe Acrobat or Adobe Acrobat Reader DC/Classic in any version.
-
Extract the exact installed version numberNote the full version string displayed in the About dialog (for example, 20.001.30018 or 17.011.30145). Record all four digit groups precisely.Affected if Version cannot be determined from the About dialog or file properties.
-
Compare version against affected rangesCheck if the installed version falls within any of these ranges: 15.008.20082 through 20.013.20074; 17.011.30059 through 17.011.30188; 20.001.30005 through 20.001.30018. Use a version comparison tool or manually compare each numeric segment.Affected if The installed version is equal to or greater than the minimum AND equal to or less than the maximum of any affected range listed.
-
Identify product variantConfirm whether the installation is Adobe Acrobat (full), Adobe Acrobat Reader (free), or Adobe Acrobat DC (subscription model). Check the title bar of the application or the About dialog which displays the product name.Affected if The product is Adobe Acrobat, Adobe Acrobat Reader, or Adobe Acrobat DC in any of the affected versions.
-
Assess exposure to certified PDFsDetermine if the environment routinely opens or processes certified (digitally signed) PDF documents. Certified PDFs display a blue ribbon icon in the signature panel. Check whether workflows involve reviewing or approving certified documents from external sources.Affected if The software is vulnerable AND the user or organization works with certified PDF documents.
A user is affected if Adobe Acrobat or Adobe Acrobat Reader DC/Classic is installed with a version number falling within any of the specified affected ranges and the software is used to handle certified PDF documents.
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.
From vendor dataUpdate Adobe Acrobat Reader DC to a patched version beyond 2020.013.20074, 2020.001.30018, or 2017.011.30188. Avoid opening untrusted PDF files until the update is applied.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28546 — 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-28546 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