CVE-2026-47919
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 a Use After Free 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 confidenceAdobe Acrobat Reader contains a Use After Free (UAF) memory corruption vulnerability in versions 24.001.30365, 26.001.21651 and earlier. When the application frees memory but continues to use a pointer to that memory, an attacker can potentially overwrite the freed memory with malicious data. By tricking a user into opening a specially crafted PDF file, an attacker could achieve arbitrary code execution 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>= 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
- 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 or ReaderCheck Program Files or Program Files (x86) for Adobe Acrobat or Adobe Acrobat Reader folders, or query the Windows Registry under HKLM\SOFTWARE\Adobe or HKLM\SOFTWARE\WOW6432Node\Adobe for installed productsAffected if Adobe Acrobat or Adobe Acrobat Reader is installed on the system
-
Determine installed versionRight-click the installed Acrobat or Reader executable (e.g., AcroRd32.exe or AcroTray.exe), select Properties, and check the File Version field on the Details tab, or use the command: wmic product where "name like 'Adobe Acrobat%'" get versionAffected if A version number is returned from the installed executable or registry
-
Compare version against affected rangesCompare the installed version number to the affected ranges: Adobe Acrobat Dc and Adobe Acrobat Reader Dc versions 15.008.20082 through 26.001.21661 (inclusive), and Adobe Acrobat versions 24.0.0 through 24.001.30382 (inclusive)Affected if The installed version falls within or equals any of these ranges: >= 15.008.20082 and < 26.001.21662 for Acrobat/Reader Dc, or >= 24.0.0 and < 24.001.30383 for Adobe Acrobat
If Adobe Acrobat or Reader is installed and the version falls within the affected ranges listed above, the environment is vulnerable to CVE-2026-47919.
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. Until patched, advise users not to open PDF files from untrusted sources and consider disabling JavaScript execution in Acrobat Reader settings.
Acrobat DC/Reader DC: 26.001.21662 or later; Acrobat (2024): 24.001.30383 or later
- Close any running Adobe Acrobat or Adobe Acrobat Reader instances
- Navigate to the official Adobe download page at helpx.adobe.com or use the Adobe Creative Cloud desktop application
- Download the appropriate fixed version for your product: For Acrobat DC/Acrobat Reader DC: version 26.001.21662 or later; For Acrobat (2024, version 24.x): version 24.001.30383 or later
- Run the installer and follow the on-screen prompts to complete the upgrade
- Restart your computer if prompted by the installer
- Verify the installed version by opening Adobe Acrobat or Reader and navigating to Help > About Adobe Acrobat (or Reader) to confirm the version number matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47919 — 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-47919 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