CVE-2026-36574
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 DLL hijacking vulnerability in Wassimulator (GitHub) CactusViewer v2.3.0 allows attackers to escalate privileges and execute arbitrary code via a crafted DLL.
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 confidenceA DLL hijacking vulnerability in CactusViewer v2.3.0 allows attackers to place a malicious DLL in a location where the application searches for DLLs during load, enabling privilege escalation to execute arbitrary code with elevated privileges.
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 CactusViewer installationSearch for 'CactusViewer.exe' in common installation directories such as C:\Program Files\, C:\Program Files (x86)\, or the user's AppData folder. Use command: dir /s C:\CactusViewer.exe or check Program Files directories manually.Affected if CactusViewer.exe is found on the system
-
Identify installed versionRight-click on CactusViewer.exe, select Properties, then view the Details tab to see the File Version. Alternatively, right-click and select 'Open file location' then check version info.Affected if Version is 2.3.0 (or any version where DLLs are loaded without full paths)
-
Check Windows Safe DLL Search Mode statusOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SafeDllSearchMode. Value 1 = enabled (safer), 0 = disabled.Affected if SafeDllSearchMode is set to 0 (disabled)
-
Identify writable directories in DLL search pathCheck directories from which CactusViewer loads DLLs. Use Process Monitor (Sysinternals) to trace DLL load events, or manually check common DLL search paths: application directory, current working directory, System32, Windows, PATH directories.Affected if Any directory in the DLL search path is writable by unprivileged users (excluding admin-only folders like System32)
-
Verify DLL loading behaviorLaunch CactusViewer.exe while monitoring with Process Monitor, filtering by CactusViewer.exe and Operation=CreateFile/LoadImage. Check if DLLs are loaded using relative paths rather than explicit full paths.Affected if Application loads DLLs without full paths from directories in the search order
User is affected if CactusViewer v2.3.0 is installed AND Windows Safe DLL Search Mode is disabled AND writable directories exist in the DLL search path where an attacker could place a malicious 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.
From vendor dataEnsure the application loads DLLs from secure, trusted locations only (use full path specifications), enable Safe DLL Search Mode, and obtain an official patch from the vendor if available.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36574 — 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-36574 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