CVE-2026-47923
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 versions 24.001.30365, 26.001.21651 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to disclose sensitive information. 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 confidenceAcrobat Reader contains an out-of-bounds read vulnerability allowing disclosure of sensitive memory contents when a user opens a maliciously crafted file. The vulnerability exists in versions 24.001.30365, 26.001.21651 and earlier.
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, < 26.001.21662>= 15.008.20082, < 26.001.21662>= 24.0.0, < 24.001.30383CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Check Adobe Acrobat versionOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat (or About Adobe Acrobat Reader) to view the installed version number shown in the dialog.Affected if The displayed version is 15.008.20082 or higher but lower than 26.001.21662 for Acrobat/Reader DC, or 24.0.0 or higher but lower than 24.001.30383 for Acrobat (classic)
-
Identify the exact product variantConfirm whether the installed product is Adobe Acrobat DC, Adobe Acrobat Reader DC, or Adobe Acrobat (classic) by checking the product name in the About dialog or the application name in Programs and Features.Affected if The product is Acrobat DC, Acrobat Reader DC, or Acrobat (classic) and the version falls within the affected ranges for that specific variant
-
Assess PDF processing exposureDetermine if the affected Adobe application is used to open PDF files from external or untrusted sources, such as email attachments, web downloads, or files from untrusted users, since exploitation requires parsing a specially crafted malicious PDF.Affected if The system processes PDF files from untrusted or external sources using the vulnerable Adobe product
A system is affected if Adobe Acrobat, Acrobat Reader DC, or Acrobat DC is installed with a version between 15.008.20082 and 26.001.21661 (for DC variants) or between 24.0.0 and 24.001.30382 (for classic Acrobat), and the application is used to 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 · scoped24.001.3038326.001.21662
Update Adobe Acrobat Reader to the latest patched version to remediate this vulnerability; users should avoid opening untrusted PDF files until the update is applied.
Acrobat DC/Reader DC: 26.001.21662 or later; Acrobat (classic): 24.001.30383 or later
- Identify which Adobe product is installed: Acrobat DC, Acrobat Reader DC, or Acrobat (classic)
- Check the current installed version in the application (Help > About Adobe Acrobat/Reader)
- For Acrobat DC or Acrobat Reader DC: Download and install version 26.001.21662 or later from Adobe's official website
- For Acrobat (classic): Download and install version 24.001.30383 or later from Adobe's official website
- Restart the application after installation
- Verify the installed version matches or exceeds the fixed version
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-2026-47923 — 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-2026-47923 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