Skip to main content
VulnerabilityPublished

CVE-2025-55187: DriveLock · Improper Privilege Management

Source CVE Database V5

0

Not known to be exploited · CVSS 9.9 Critical · fixed in 25.1.4 : patch affected systems as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 25.1.4, 24.2.6, 24.1.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 the risk posed by CVE-2025-55187, European organizations should take the following specific actions: 1) Immediately identify all systems running affected versions of DriveLock (24.1.4 before 24.1.5, 24.2.5 before 24.2.6, and 25.1.2 before 25.1.4) through asset management and software inventory tools. 3) Until patches are applied, implement strict access controls to limit user permissions and reduce the attack surface, including restricting local administrator rights and enforcing the principle of least privilege. 4) Monitor endpoint logs and security alerts for unusual privilege escalation attempts or suspicious activity indicative of exploitation attempts. 5) Employ network segmentation and endpoint detection and response (EDR) solutions to detect and contain potential lateral movement resulting from privilege escalation. 6) Conduct user awareness training to reduce the risk of initial compromise vectors that could lead to exploitation, such as phishing. 7) Review and harden DriveLock configuration settings to ensure they follow security best practices and do not inadvertently expose privilege escalation vectors. 8) Engage with DriveLock support or vendor resources for guidance and to confirm patch availability and deployment strategies.

Description

In DriveLock 24.1.4 before 24.1.5, 24.2.5 before 24.2.6, and 25.1.2 before 25.1.4, attackers can gain elevated privileges.

References

Community reviews

Loading reviews…