CVE-2026-26306
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 installer for OM Workspace (Windows Edition) Ver 2.4 and earlier insecurely loads Dynamic Link Libraries (DLLs), which could allow an attacker to execute arbitrary code with the privileges of the user invoking the installer.
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 confidenceThe OM Workspace (Windows Edition) installer Ver 2.4 and earlier performs insecure DLL loading, searching user-controlled or insecure directories for Dynamic Link Libraries. An attacker who can place a malicious DLL in a directory the installer searches (such as the current working directory or an uncontrolled PATH location) can achieve arbitrary code execution with the privileges of the user running the installer.
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.0/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.
-
Identify the OM Workspace installer versionLocate the OM Workspace installer executable (typically named something like OMWS_Setup.exe or similar) and check its file properties. In Windows Explorer, right-click the file, select Properties, and look at the Details tab for the Version or File version field. Alternatively, run the installer with a version flag if supported (such as /version or -v).Affected if The version listed is 2.4 or any version lower than 2.4 (for example, 2.3, 2.2, 1.x).
-
Verify the installer directory permissionsRight-click the folder containing the OM Workspace installer, select Properties, go to the Security tab, and examine which users or groups have Write or Modify permissions. Use icacls from Command Prompt (e.g., icacls "C:\path\to\installer") to list explicit permissions.Affected if Users other than the administrator or the current user have Write or Modify access to the directory holding the installer.
-
Check for writable locations in the system PATHOpen Command Prompt and run echo %PATH% to display all directories in the PATH environment variable. For each directory listed, run icacls to check permissions (e.g., icacls "C:\Windows\System32"). Identify any directories writable by standard users or untrusted accounts.Affected if Any directory in the system or user PATH is writable by unprivileged or untrusted users.
-
Assess current working directory risk at install timeBefore running the installer, open Command Prompt and run cd to display the current working directory. Check this directory's permissions using icacls to determine if other users can write files to it.Affected if The current working directory from which the installer is launched is writable by other users or resides in a shared/user-controlled location such as Downloads or Desktop.
You are affected if the OM Workspace installer version is 2.4 or earlier AND the installer is run from or located in a directory writable by untrusted users, or any directory in the system PATH is writable by unprivileged users.
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 the vendor patch when available. Until then, run the installer from a clean, controlled directory and ensure the directory containing the installer is not writable by unprivileged users. Consider application whitelisting to block unsigned DLL loading.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26306 — 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-26306 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