CVE-2026-5491

Received Received - Intake

Directory Traversal in DriveLock Exposes Sensitive Data

Publication date: 2026-07-29

Last updated on: 2026-07-30

Assigner: Zero Day Initiative

Description

DriveLock Directory Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of DriveLock. Authentication is not required to exploit this vulnerability. The specific flaw exists within the web service, which listens on TCP port 6067 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-28722.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-29

Last Modified

2026-07-30

Generated

2026-08-19

AI Q&A

2026-07-30

EPSS Evaluated

2026-08-18

NVD

CVE-2026-5491

Affected Vendors & Products

Vendor	Product	Version / Range
drivelock	drivelock	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-22	The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

Executive Summary

This is a directory traversal vulnerability in DriveLock that allows remote attackers to read sensitive files without authentication. The flaw exists in the web service running on TCP port 6067 due to improper path validation before file operations. Attackers can exploit this to access information in the context of the service account.

Detection Guidance

Check if the DriveLock web service is listening on TCP port 6067. Use commands like 'netstat -ano | findstr 6067' on Windows or 'ss -tulnp | grep 6067' on Linux to verify. If the service is running, test for directory traversal by attempting to access files outside expected directories using crafted URLs.

Impact Analysis

An attacker could exploit this to read sensitive files on the system running DriveLock, potentially exposing confidential data such as configuration files, user credentials, or other restricted information. Since no authentication is required, any remote attacker can attempt this attack.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating compliance requirements under GDPR (data protection) and HIPAA (health information privacy). Organizations using DriveLock may face regulatory penalties if this flaw results in data breaches.

Mitigation Strategies

Disable or restrict access to the DriveLock web service on TCP port 6067. Apply patches or updates from DriveLock if available. Implement network-level controls to block external access to port 6067. Monitor for unusual file access patterns or information disclosure attempts.

Hi! I’m here to help you understand CVE-2026-5491. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70