CVE-2023-26408
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 · uneditedAdobe Acrobat Reader versions 23.001.20093 (and earlier) and 20.005.30441 (and earlier) are affected by an Improper Access Control vulnerability that could result in 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 confidenceAdobe Acrobat Reader contains an Improper Access Control vulnerability in versions 23.001.20093 and earlier, and 20.005.30441 and earlier, that allows arbitrary code execution in the context of the current user when a victim opens a maliciously 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.3005, <= 20.005.30441>= 15.008.20082, <= 23.001.20093>= 20.001.3005, <= 20.005.30441>= 15.008.20082, <= 23.001.20093CVSS 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 Reader is installedCheck for Adobe Acrobat Reader in typical installation paths such as C:\Program Files\Adobe\Adobe Acrobat Reader DC\ or C:\Program Files (x86)\Adobe\Adobe Acrobat Reader DC\, or use Control Panel > Programs and Features to list installed software.Affected if Adobe Acrobat Reader appears in installed programs
-
Obtain the installed version numberRight-click the Acrobat Reader executable (e.g., AcroRd32.exe or AcroRd64.exe) in the installation folder, select Properties, and view the Details tab for the Product Version. Alternatively, open Acrobat Reader and navigate to Help > About Adobe Acrobat Reader.Affected if Unable to determine version indicates potential incomplete installation or non-Adobe PDF viewer in use
-
Compare version against affected rangesMatch the installed version to the following vulnerable ranges: 20.001.3005 through 20.005.30441 (Classic version), or 15.008.20082 through 23.001.20093 (DC version). Any version within these inclusive ranges is affected.Affected if Installed version falls within 20.001.3005-20.005.30441 or 15.008.20082-23.001.20093
-
Confirm Adobe is the default PDF handlerRight-click any PDF file, select Properties, and verify the 'Opens with' field shows Adobe Acrobat Reader. Alternatively, go to Settings > Apps > Default Apps and check the PDF file type association.Affected if Adobe Acrobat Reader is set as the default application for opening PDF files
A user is affected if Adobe Acrobat Reader (Classic or DC version) is installed with a version number within the ranges 20.001.3005-20.005.30441 or 15.008.20082-23.001.20093 and is used to 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 to the latest version beyond 23.001.20093 or 20.005.30441 to remediate this vulnerability.
Adobe Acrobat Reader 23.002.20093 (Continuous) or 20.005.30449 (Classic)
- 1. Determine which Adobe Acrobat/Acrobat Reader track you are using (Continuous or Classic) by opening Adobe Acrobat/Reader and navigating to Help > About Adobe Acrobat/Reader. Note the version number.
- 2. For Continuous track users: If your version is 23.001.20093 or earlier, upgrade to version 23.002.20093 or later.
- 3. For Classic track users: If your version is 20.005.30441 or earlier, upgrade to version 20.005.30449 or later.
- 4. Download the latest version from the official Adobe Acrobat download page at https://get.adobe.com/reader/ or https://get.adobe.com/acrobat/
- 5. Close all Adobe Acrobat/Reader instances before running the installer.
- 6. Run the installer and follow the on-screen prompts to complete the upgrade.
- 7. After installation, verify the new version by checking Help > About to confirm the fix is applied.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26408 — 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-2023-26408 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