CVE-2026-26306: OM Digital Solutions OM Workspace (Windows Edition) · Uncontrolled Search Path Element
Affects OM Digital Solutions OM Workspace (Windows Edition)Source CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OM Digital Solutions CorporationOM Workspace (Windows Edition) | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, organizations should: 1) Upgrade OM Workspace to a version later than 2.4 once a patched release is available from OM Digital Solutions Corporation. 2) Until a patch is released, restrict installation privileges to trusted administrators and avoid running the installer from untrusted directories. 3) Implement application whitelisting to prevent unauthorized DLLs from loading during installation. 4) Use Windows security features such as Safe DLL Search Mode and enable DLL Safe Search Mode via system policies to reduce the risk of DLL hijacking. 5) Educate users about the risks of running installers from unverified sources and the importance of verifying software integrity. 6) Monitor systems for unusual DLL loading behavior or unexpected processes spawned during installation. 7) Employ endpoint detection and response (EDR) solutions to detect and block suspicious activity related to DLL hijacking. These steps go beyond generic advice by focusing on controlling the installation environment and leveraging Windows-specific security controls.
Description
The 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.