CVE-2025-26155
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 · uneditedNCP Secure Enterprise Client 13.18 and NCP Secure Entry Windows Client 13.19 have an Untrusted Search Path vulnerability.
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 confidenceUntrusted Search Path vulnerability in NCP Secure Enterprise Client 13.18 and NCP Secure Entry Windows Client 13.19 allows attackers to execute malicious code via DLL hijacking by placing malicious DLLs in directories that the application searches when loading libraries.
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.19= 13.18CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify installed NCP client versionCheck the installed version of NCP Secure Enterprise Client or NCP Secure Entry Windows Client via Windows Programs and Features, or by querying the application's About or Help menuAffected if Version shown is 13.18 (Enterprise Client) or 13.19 (Entry Client)
-
Verify DLL search path configurationUse process monitoring tools or check application configuration to see which directories the NCP client searches when loading DLLs. Look for whether the current working directory, temp folder, or user-writable paths are included in the DLL search orderAffected if The application's DLL search path includes directories writable by standard users (such as current directory, Downloads, or temp folders)
-
Inspect common DLL search directories for suspicious filesExamine directories that the NCP client may query for DLLs, particularly the application installation directory, system directories, and any user-writable directories in the search path. Look for unexpected or recently placed DLL files with names matching commonly hijacked DLLsAffected if Unexpected DLL files exist in directories the NCP client uses for library loading, especially in writable locations
-
Check application behavior on startupMonitor the NCP client process during startup using tools that log DLL loading events, noting which DLLs are loaded and from which pathsAffected if The application loads DLLs from directories outside the secure, controlled installation path
A user is affected if they have NCP Secure Enterprise Client version 13.18 or NCP Secure Entry Windows Client version 13.19 installed AND the application's DLL search path includes user-writable directories where malicious DLLs could be placed.
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 dataApply vendor patch when available; ensure the application uses secure, controlled paths for DLL loading and implement application control policies to prevent unauthorized DLL placement.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26155 — 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-2025-26155 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