CVE-2025-55187 Privilege escalation in n/a
Critical 9.9
Published
Updated
Check this codebase for CVE-2025-55187 and fix it if it is affected.
What it is: CVE-2025-55187 is a critical vulnerability in n/a, published on 26 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55187 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2025-55187/ (Markdown: https://insights.sbomify.com/CVE-2025-55187/index.md)
Attackers can gain elevated privileges in DriveLock security software, requiring an upgrade to patched versions.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-55187?
CVE-2025-55187 is a critical vulnerability in n/a, published on 26 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-269
Which versions are affected by CVE-2025-55187?
It affects 1 product.
Products include Drivelock Drivelock.
How do I fix CVE-2025-55187?
No fix has been published for CVE-2025-55187 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-55187 being exploited?
There is no known exploitation of CVE-2025-55187 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-825q-gjjg-wpfr.