# CVE-2026-5492: DriveLock Directory Traversal Information Disclosure Vulnerability

> Authenticated attackers can exploit a path traversal flaw in the DriveLock web service to disclose sensitive information.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-3mgm-5g78-fwgq

## What is CVE-2026-5492?

CVE-2026-5492 is a medium-severity path traversal vulnerability in DriveLock, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

DriveLock Directory Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of DriveLock. Authentication is required to exploit this vulnerability.

The specific flaw exists within the web service, which listens on TCP port 4568 by default. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to disclose information in the context of the service account. Was ZDI-CAN-28713.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-5492?


## How do I fix CVE-2026-5492?

No fix has been published for CVE-2026-5492 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5492 being exploited?

There is no known exploitation of CVE-2026-5492 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5492 and fix it if it is affected.

What it is: CVE-2026-5492 is a medium-severity path traversal vulnerability in DriveLock, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5492 in the wild and no public exploit code.

Affected product: DriveLock. 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-2026-5492/ (Markdown: https://insights.sbomify.com/CVE-2026-5492/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5492
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5492
- OSV: https://osv.dev/vulnerability/CVE-2026-5492

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5492/
Summaries are generated and may contain mistakes; the official description above is the record.