CVE-2026-3775
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 · uneditedThe application's update service, when checking for updates, loads certain system libraries from a search path that includes directories writable by low‑privileged users and is not strictly restricted to trusted system locations. Because these libraries may be resolved and loaded from user‑writable locations, a local attacker can place a malicious library there and have it loaded with SYSTEM privileges, resulting in local privilege escalation and arbitrary code execution.
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 confidenceThe application's update service loads system libraries from a search path that includes directories writable by low-privileged users rather than restricting to trusted system locations, allowing a local attacker to place a malicious DLL in a writable directory that gets loaded with SYSTEM 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<= 13.2.2.24014>= 14.0.0.33046, <= 14.0.2.33402>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.4.1.27687>= 2025.1.0.27937, <= 2025.3.0.35737<= 2025.3.0.35737CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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.
-
Check if Foxit PDF Editor or Reader is installedLook for Foxit software in the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or check common installation paths such as C:\Program Files\Foxit Software\ or C:\Program Files (x86)\Foxit Software\Affected if Foxit PDF Editor or Reader is installed on the system
-
Identify the installed Foxit versionOpen the installed Foxit application, then navigate to Help > About Foxit PDF Editor/Reader to view the exact version number, or check the Uninstall registry key for the DisplayVersion valueAffected if The version falls within any of these affected ranges: <= 13.2.2.24014, >= 14.0.0.33046 through <= 14.0.2.33402, >= 2023.1.0.15510 through <= 2023.3.0.23028, >= 2024.1.0.23997 through <= 2024.4.1.27687, >= 2025.1.0.27937 through <= 2025.3.0.35737 for Foxit PDF Editor; or <= 2025.3.0.35737 for Foxit
-
Determine if Foxit update service is presentCheck Windows Services (services.msc) for a Foxit update-related service such as 'Foxit Reader Update Service' or 'Foxit PDF Editor Update Service', or check for the update service executable in the Foxit installation directoryAffected if The Foxit update service component is installed and available on the system
-
Verify the update service runs with elevated privilegesOpen Services, locate the Foxit update service, right-click and select Properties, then check the 'Log On' account - SYSTEM or LocalSystem indicates elevated privilegesAffected if The update service is configured to run under the SYSTEM or LocalSystem account
If Foxit PDF Editor or Reader is installed with a version matching the affected ranges AND the update service component is present and runs with SYSTEM privileges, the environment is vulnerable to DLL hijacking via user-writable directories.
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.
From vendor dataRestrict library loading to trusted system directories (e.g., application directory, System32) and remove user-writable paths from the search order, or run the update service with reduced privileges and implement library integrity validation.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3775 — 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-3775 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