Rapid7 Velociraptor
CVE-2025-14728
MEDIUM
Severity by source
AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
Network-reachable rogue client (PR:N) but trailing-dot/%2E directory constraint and limited write placement make it AC:H; writes escape datastore boundary (S:C) with integrity-only impact (I:H, C:N, A:N).
Primary rating from Vendor (rapid7).
CVSS VectorVendor: rapid7
Lifecycle Timeline
2DescriptionCVE.org
Rapid7 Velociraptor versions before 0.75.6 contain a directory traversal issue on Linux servers that allows a rogue client to upload a file which is written outside the datastore directory. Velociraptor is normally only allowed to write in the datastore directory. The issue occurs due to insufficient sanitization of directory names which end with a ".", only encoding the final "." AS "%2E".
Although files can be written to incorrect locations, the containing directory must end with "%2E". This limits the impact of this vulnerability, and prevents it from overwriting critical files.
AnalysisAI
Directory traversal in Rapid7 Velociraptor servers running on Linux before 0.75.6 lets a rogue enrolled client upload a file that is written outside the server's datastore directory, breaching the assumption that Velociraptor only writes within the datastore. The flaw stems from insufficient sanitization of directory names that end with a trailing dot, where only the final '.' is encoded as '%2E', but the impact is constrained because the containing directory must itself end in '%2E', which the vendor states prevents overwriting critical files. The vector (AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N) reflects high attack complexity and integrity-only impact, EPSS is low at 0.56% (44th percentile), there is no KEV listing, and publicly available exploit code exists, so this is a genuine but constrained medium-severity issue rather than a high-urgency crisis.
Technical ContextAI
Velociraptor is Rapid7's endpoint visibility and DFIR platform, built around a server that collects artifacts and uploaded collections from enrolled client agents into a dedicated datastore directory; the security model depends on all server-side writes being confined to that datastore. This CVE is a CWE-22 path traversal in that file-upload handling path on Linux servers: directory names ending with a '.' are insufficiently sanitized because only the final '.' is percent-encoded as '%2E', leaving traversal-capable sequences that permit the resulting path to resolve outside the datastore. The CVSS scope change (S:C) captures that the write escapes the vulnerable component's intended security boundary (the datastore), and AC:H reflects the crafted conditions needed. The CPE string cpe:2.3:a:rapid7:velociraptor:*:*:*:*:*:*:*:* indicates the affected product family across versions prior to the 0.75.6 fix, and the assessed exploitation prerequisites are a Linux Velociraptor server below 0.75.6 plus an attacker-controlled or compromised enrolled client able to initiate uploads into a directory name ending in '%2E'; Windows and other non-Linux servers are not stated to be affected.
RemediationAI
Upgrade Velociraptor server and clients to version 0.75.6 or later, which is the vendor-released fix for this directory traversal issue, and follow the advisory at https://docs.velociraptor.app/announcements/advisories/cve-2025-14728/ for the official guidance. If immediate upgrading is not possible, apply compensating controls that address the rogue-client prerequisite and the write-outside-datastore condition: tightly control and rotate client enrollment secrets and pre-approved client certificates so an unauthorized endpoint cannot enroll (trade-off: legitimate new clients must be provisioned out-of-band, which adds operational overhead), run the Velociraptor server under a dedicated low-privilege service account whose permissions are scoped only to the datastore directory so out-of-datastore writes fail or are limited (trade-off: overly tight permissions can break legitimate collection features and must be tested), and monitor or audit server-side file writes and anomalous upload artifact paths for directory components ending in '%2E' or a trailing dot (trade-off: detection depends on log coverage and may generate false positives from legitimate filenames). Note that no in-product configuration toggle fully eliminates the traversal path, so upgrading remains the primary remediation, and there is no indication that Windows or non-Linux servers require mitigation.
More in Velociraptor
View allPrivilege escalation in Velociraptor's notebook VQL execution path allows analyst-role users to bypass the COLLECT_CLIEN
Privilege escalation in Rapid7 Velociraptor lets any user permitted to schedule client monitoring artifacts run otherwis
Privilege escalation in Rapid7 Velociraptor allows an authenticated user holding only the 'investigator' role to execute
Privilege escalation to administrator in Rapid7 Velociraptor (all versions before 0.77.2) allows an authenticated low-pr
Velociraptor allows collection of VQL queries packaged into Artifacts from endpoints. These artifacts can be used to do
Privilege escalation in Velociraptor allows any user with the NOTEBOOK_EDIT permission - typically an analyst-level role
Rapid7 Velociraptor allows users to be created with different privileges on the server. Rated high severity (CVSS 8.8),
Privilege escalation in Rapid7 Velociraptor's multi-tenant org management allows child org administrators to delete any
Remote code execution in Rapid7 Velociraptor server (primarily Linux) allows authenticated clients to write malicious me
Cross-site scripting in Velociraptor's web GUI arises from unsanitized URL scheme handling in URL-typed table columns, e
Multi-tenancy authorization bypass in Velociraptor before 0.76.3 allows authenticated GUI users to execute VQL queries a
Template injection in Velociraptor's notebook backup restoration pipeline allows a low-privileged NOTEBOOK_EDITOR user t
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today