CVE-2025-59684: DigiSign DigiSigner ONE · Uncontrolled Search Path Element
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
AI-suggested
To mitigate this vulnerability, European organizations should first verify if DigiSign DigiSigner ONE 1.0.4.60 is deployed within their environment. Implement application whitelisting and use endpoint protection solutions capable of detecting suspicious DLL loads. Organizations should also educate users about the risks of running applications from untrusted locations and avoid launching DigiSigner ONE from network shares or temporary directories. Monitoring for unusual process behavior or unexpected DLL loads can help detect exploitation attempts. Additionally, organizations should engage with DigiSign for updates or patches and plan to apply them promptly once released. Employing software restriction policies or Windows Defender Application Control to enforce trusted DLL loading paths can further reduce risk.
Description
DigiSign DigiSigner ONE 1.0.4.60 allows DLL Hijacking.