CVE-2026-2516
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 · uneditedA vulnerability was identified in Unidocs ezPDF DRM Reader and ezPDF Reader 2.0/3.0.0.4. This affects an unknown part in the library SHFOLDER.dll. Such manipulation leads to uncontrolled search path. The attack needs to be performed locally. Attacks of this nature are highly complex. It is indicated that the exploitability is difficult. The exploit is publicly available and might be used. Upgrading the affected component is recommended. The vendor explains: "[W]e have already addressed similar DLL search path vulnerability patterns through prior security updates. (...) Users are advised to use the latest version provided by the vendor."
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 confidenceA DLL search order hijacking vulnerability in Unidocs ezPDF DRM Reader and ezPDF Reader (versions 2.0/3.0.0.4) in the SHFOLDER.dll library allows local attackers to execute arbitrary code by placing malicious DLLs in the application search path, which the vulnerable application will load without proper validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/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.
-
Locate ezPDF Reader installationSearch for ezPDF Reader or ezPDF DRM Reader in Program Files directories (C:\Program Files\, C:\Program Files (x86)\) and check for folders containing 'ezPDF' or 'unidocs'. Also query the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for display names containing 'ezPDF' or 'Unidocs'.Affected if The application is found in the system
-
Identify installed versionRight-click the main executable (typically named ezPDF.exe or similar in the installation folder), select Properties, and check the 'File version' or 'Product version' field in the Details tab. Alternatively, examine the version listed in the registry uninstall entry found in Step 1.Affected if The version is 2.0 or 3.0.0.4 (or any version within the 2.x-3.0.0.4 range)
-
Verify presence of vulnerable SHFOLDER.dllNavigate to the application installation directory found in Step 1 and search for a file named SHFOLDER.dll. Use command: dir /s "C:\Program Files*\*SHFOLDER.dll" or inspect the application directory manually.Affected if SHFOLDER.dll exists in the application directory or subfolders
-
Check application directory write accessRight-click the main application folder found in Step 1, select Properties, go to the Security tab, and verify which users or groups have Write or Modify permissions. From command line: icacls "<application_path>" | findstr /i "(F) (M) (W)"Affected if Standard users or the current user has Write or Modify permissions to the application directory (allows attacker to place malicious DLLs)
-
Scan for suspicious DLLs in application pathList all DLL files in the application directory: dir "<application_path>\*.dll". Compare against known legitimate DLLs (like SHFOLDER.dll) and look for unexpected or recently created DLLs that may have been planted.Affected if Unexpected DLLs are present in the application directory that were not part of the original installation
You are affected if Unidocs ezPDF Reader or ezPDF DRM Reader versions 2.0 or 3.0.0.4 is installed and the application directory contains the vulnerable SHFOLDER.dll with write permissions allowing untrusted DLL placement.
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 · scopedUpgrade to the latest version of ezPDF Reader as recommended by the vendor; verify that secure DLL loading practices are implemented to prevent search path manipulation.
Latest version available from Unidocs (vendor states prior security updates addressed similar DLL search path vulnerabilities)
- 1. Navigate to the official Unidocs website at www.unidocs.com to download the latest version of ezPDF DRM Reader or ezPDF Reader
- 2. Locate the current version of ezPDF Reader installed on your system (typically in Help > About or application properties)
- 3. If your current version is 2.0 or 3.0.0.4, proceed with downloading the most recent version available from the vendor
- 4. Uninstall the current version of ezPDF Reader from your system
- 5. Install the newly downloaded latest version of ezPDF Reader
- 6. Restart any running instances of the application
- 7. Verify the installed version matches the latest release available from Unidocs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2516 — 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-2516 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