Privilege escalation via writable-directory DLL hijacking
Published Aug 17, 2026 · Updated Aug 18, 2026
DLL hijacking in CGM ISIS MED 2510.1.0.20 allows local users to execute code by planting dfshim.dll in a writable application folder. SILoader.exe searches for the missing dfshim.dll and loads an attacker-supplied file from a user-writable per-user application directory. A local low-privileged user must write the DLL and restart the application; the payload then runs with the application's privileges.
Summary
What happened
DLL hijacking in CGM ISIS MED 2510.1.0.20 allows local users to execute code by planting dfshim.dll in a writable application folder. SILoader.exe searches for the missing dfshim.dll and loads an attacker-supplied file from a user-writable per-user application directory. A local low-privileged user must write the DLL and restart the application; the payload then runs with the application's privileges.
The record
- CVE
- CVE-2026-50773
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-427, T1574.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- dfshim.dll hijacking proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo