CVE-2023-26407
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 Input Validation 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 · high confidenceThis is an improper input validation vulnerability in Adobe Acrobat Reader that allows arbitrary code execution when a user opens a maliciously crafted PDF file. The vulnerability exists due to insufficient validation of input data within PDF files, enabling an attacker to execute code in the context of the current user's privileges.
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.
-
Identify installed Adobe Acrobat Reader versionOpen Adobe Acrobat Reader, then go to Help > About Adobe Acrobat Reader (Windows) or Acrobat Reader > About Adobe Acrobat Reader (macOS). Alternatively, check the Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\<version> or the macOS application bundle info.plist.Affected if The version falls within the affected ranges: 20.001.3005 to 20.005.30441 for classic versions, or 15.008.20082 to 23.001.20093 for DC versions.
-
Confirm product variant (Classic vs DC)Check whether the installed product is Adobe Acrobat Reader (Classic) or Adobe Acrobat Reader DC by examining the product name in the About dialog or registry key path.Affected if The variant matches the affected version ranges for that specific product type.
-
Verify version is within vulnerable rangeCompare the installed four-part version number (for example, 20.005.30400) against the affected range boundaries: minimum 20.001.3005 / 15.008.20082 and maximum 20.005.30441 / 23.001.20093.Affected if The installed version is greater than or equal to the minimum AND less than or equal to the maximum for the applicable range.
The environment is affected if Adobe Acrobat Reader or Acrobat Reader DC is installed with a version number that falls within the specified vulnerable ranges and users open PDF files from untrusted sources.
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 versions newer than 23.001.20093 or 20.005.30441. Avoid opening untrusted or unexpected PDF files from unknown sources.
Upgrade to Adobe Acrobat/Reader version 23.002.x or later (for 23.x track) or version 20.xx.xxxx or later (for 20.x track). The fixed releases are versions subsequent to 23.001.20093 and 20.005.30441.
- 1. Open Adobe Acrobat or Acrobat Reader on the affected system
- 2. Navigate to Help > Check for Updates or use the built-in update mechanism
- 3. Allow the application to check for and install available updates
- 4. Alternatively, download the latest version of Adobe Acrobat Reader from the official Adobe website (get.adobe.com/reader)
- 5. Ensure the updated version is greater than 20.005.30441 for the 20.x track or greater than 23.001.20093 for the 23.x track
- 6. Restart the application after updating
- 7. Verify the update was successful by checking Help > About Adobe Acrobat Reader
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-2023-26407 — 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-26407 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