CVE-2026-47961
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 · high confidenceAdobe Acrobat Reader contains an out-of-bounds read vulnerability in versions 24.001.30365, 26.001.21651 and earlier. The vulnerability allows a specially crafted PDF file to trigger an out-of-bounds memory read, potentially exposing sensitive memory contents to an attacker. Exploitation requires user interaction where the victim must open a malicious 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< 24.001.30383< 26.001.21662< 26.001.21662CVSS 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 if Adobe Acrobat Reader is installedOn Windows, open Control Panel > Programs and Features and look for 'Adobe Acrobat Reader' in the list of installed software. On macOS, open Finder > Applications and check for Adobe Acrobat Reader.Affected if Adobe Acrobat Reader appears in the installed programs list
-
Determine the installed version numberIn Windows, right-click on Adobe Acrobat Reader in the Start menu, select 'Properties', and view the 'Version' field under the 'Details' tab. Alternatively, launch Adobe Acrobat Reader, go to Help > About Adobe Acrobat Reader to display the version.Affected if The version displayed is lower than 26.001.21662
-
Check for Adobe Acrobat (full application) version if installedIf Adobe Acrobat (not Reader) is installed instead, open the application and go to Help > About Adobe Acrobat. Note the version number displayed.Affected if The version is lower than 24.001.30383 or lower than 26.001.21662 (whichever branch applies)
-
Verify PDF handling capability is activeConfirm that Adobe Acrobat Reader is set as the default PDF handler or that the application can open PDF files. This can be checked by right-clicking any PDF file, selecting 'Open with', and confirming Adobe Acrobat Reader is available as an option.Affected if Adobe Acrobat Reader is set to handle PDF files and can be used to open PDF documents
A user is affected if Adobe Acrobat Reader version 26.001.21662 or later (or Adobe Acrobat version 24.001.30383/26.001.21662 or later) is NOT installed and the application can 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 · scoped24.001.3038326.001.21662
Update Adobe Acrobat Reader to the latest patched version provided by Adobe. Since exploitation requires user interaction, organizations should consider user awareness training regarding opening untrusted PDF attachments, though the primary remediation is applying the vendor security update.
Adobe Acrobat 24.001.30383 or later; Adobe Acrobat 26.001.21662 or later (or Acrobat Reader 26.001.21662 or later)
- Identify whether you have Adobe Acrobat or Adobe Acrobat Reader installed
- Determine your current version by opening the application and navigating to Help > About Adobe Acrobat/Reader
- For Adobe Acrobat users: Upgrade to version 24.001.30383 or later, OR version 26.001.21662 or later
- For Adobe Acrobat Reader users: Upgrade to version 26.001.21662 or later
- Download the latest version from the official Adobe website at helpx.adobe.com or use the application's built-in update feature (Help > Check for Updates)
- Restart the application after installation
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-47961 — 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-47961 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