CVE-2025-55187: 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

This month

CRITICAL 9.9DOWNGRADE

CVE-2025-55187 is a critical-severity flaw (CVSS 9.9) affecting drivelock. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.9 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 61%)
CISA exploited list	No
Weakness	CWE-269
Published	2025-09-26
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: drivelock

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-09-26 15:16 UTCPublished CVE record published
2026-06-17 09:41 UTCUpdated Record last modified

drivelock drivelock DOWNGRADE

Affected: 24.1.4 · 24.2.5 · 25.1.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 24.1.4

1. Check installed version

apt-cache policy drivelock || rpm -q drivelock || drivelock --version

2. No fixed release: DOWNGRADE to a release before 24.1.4 (Debian / Ubuntu)

apt-cache madison drivelock sudo apt install drivelock=<VERSION_BEFORE_24.1.4> sudo apt-mark hold drivelock

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list drivelock sudo dnf downgrade drivelock-<VERSION_BEFORE_24.1.4> sudo dnf versionlock add drivelock

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-55187?

drivelock: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-55187 being exploited?

CVE-2025-55187 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-55187 affect?

CVE-2025-55187 affects drivelock. Severity is critical (CVSS 9.9). 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.

How urgent is CVE-2025-55187?

Priority 44/100. Critical severity

Related CVEs

CVE-2025-67793 CRITICAL 9.8 UPGRADE An issue was discovered in DriveLock 24.1 through 24.1.*, 24.2 through 24.2.*, and 25.1 before 25.1.6
CVE-2025-67781 CRITICAL 9.9 UPGRADE An issue was discovered in DriveLock 24.1 before 24.1.6, 24.2 before 24.2.7, and 25.1 before 25.1.5
CVE-2025-67790 HIGH 7.5 UPGRADE An issue was discovered in DriveLock 24.1 before 24.1.6, 24.2 before 24.2.7, and 25.1 before 25.1.5
CVE-2025-67792 HIGH 7.8 UPGRADE An issue was discovered in DriveLock 24.1 before 24.1.6, 24.2 before 24.2.7, and 25.1 before 25.1.5
CVE-2025-67789 MEDIUM 5.3 UPGRADE An issue was discovered in DriveLock 24.1 before 24.1.6, 24.2 before 24.2.7, and 25.1 before 25.1.5

References

← Back to latest CVEs