CVE-2026-47937
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 Uncontrolled Search Path Element vulnerability that could result in arbitrary code execution in the context of the current user. An attacker with high privileges could exploit this vulnerability to execute arbitrary code. Exploitation of this issue requires user interaction in that a victim must open a malicious file. Scope is changed.
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 Uncontrolled Search Path Element vulnerability where the application loads DLLs or executables using an insufficiently specified path. An attacker with high privileges can place a malicious DLL/executable in a location that Adobe Reader will search during startup, resulting in arbitrary code execution when a victim opens 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>= 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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/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.
-
Check installed Adobe Acrobat versionOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). The version number is displayed in the dialog box.Affected if The version shown is >= 15.008.20082 and < 26.001.21662 for Acrobat/Reader DC, or >= 24.0.0 and < 24.001.30383 for Acrobat (2024).
-
Verify exact build numberNote the full build number from the About dialog (for example, 26.001.21651). Compare it to the affected version ranges provided.Affected if The build number falls within the vulnerable ranges listed in the CVE.
-
Confirm product variantDetermine whether the installation is Adobe Acrobat DC, Adobe Acrobat Reader DC, or Adobe Acrobat (2024). Each has different affected version ranges.Affected if The product is Acrobat DC or Reader DC with version >= 15.008.20082 and < 26.001.21662, or Acrobat 2024 with version >= 24.0.0 and < 24.001.30383.
-
Identify DLL search path exposureExamine the Adobe application installation directory and common DLL loading directories for any writable locations where an attacker with high privileges could place a malicious DLL.Affected if A writable directory exists in or adjacent to the Adobe application path where an untrusted DLL could be placed and loaded.
You are affected if Adobe Acrobat or Reader DC version is between 15.008.20082 and 26.001.21661 (inclusive), or Acrobat 2024 version is between 24.0.0 and 24.001.30382 (inclusive), and an attacker with high privileges can place a malicious DLL in the DLL search path before the legitimate DLL.
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. Apply vendor security updates as they become available and verify the update across the enterprise.
Acrobat Dc/Reader Dc: 26.001.21662 | Acrobat: 24.001.30383
- 1. Open Adobe Acrobat or Acrobat Reader and navigate to Help > About Adobe Acrobat (or Reader) to confirm your current version number.
- 2. For Acrobat Dc and Acrobat Reader Dc: Download version 26.001.21662 or later from the official Adobe website (helpx.adobe.com).
- 3. For Acrobat (standalone): Download version 24.001.30383 or later from the official Adobe website (helpx.adobe.com).
- 4. Close all Adobe applications before running the installer.
- 5. Run the downloaded installer and follow the on-screen prompts to complete the update.
- 6. After installation, verify the version by checking Help > About to confirm you are on 26.001.21662+ (Dc products) or 24.001.30383+ (Acrobat).
- 7. Restart your computer to ensure all components are properly updated.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47937 — 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-47937 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