Description

Velociraptor allows reading Stacked result sets from the GUI.  Velociraptor's multi-tenant design stores sub orgs within the datastore directory. The path requested by the GUI is not correctly checked against the prefix deny list, allowing result sets to read from denied prefixes. In particular, a user with read access to the root org can access result sets from child orgs.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "4.9",
  "pubDate": "2026-08-12T10:17:16.940Z",
  "pubdate": "2026-08-12T10:17:16.940Z",
  "executiveSummary": "Velociraptor contains an authorization and path validation vulnerability within its GUI component that allows unauthorized access to restricted data across multi-tenant boundaries. The vulnerability specifically involves improper validation of requested paths against a prefix deny list when reading Stacked result sets.\nThe primary impact of this flaw is a security bypass within the multi-tenant architecture, where a user with read access to the root organization can arbitrarily access and read result sets belonging to child organizations stored within the datastore directory.\nThe affected product is Velociraptor, specifically impacting deployments utilizing its multi-tenant design where sub-organizations are segregated within the datastore directory structure.\nThe risk implications include unauthorized cross-tenant data disclosure, unauthorized viewing of sensitive forensic artifact data, and potential compromise of isolation guarantees between distinct sub-organizations managed by the platform.\nAn attacker must possess authenticated read access to the root organization to initiate the attack. Exploitation requires the attacker to issue crafted requests to the GUI that leverage the flawed path checking mechanism to bypass prefix deny lists and traverse into restricted sub-organization directories.",
  "technicalDetails": "The root cause of the vulnerability resides in insufficient input validation and path sanitization within the Velociraptor GUI when processing requests to read Stacked result sets. Specifically, the path requested via the graphical interface fails to correctly verify against the implemented prefix deny list.\nVelociraptor employs a multi-tenant architectural design that logically separates sub-organizations by storing their respective data within distinct subdirectories inside the core datastore directory. Under normal operational constraints, prefix deny lists are designed to restrict access boundaries between these organizational tenants.\nBecause the path validation logic fails to properly evaluate or enforce the prefix deny list against crafted requests, the security boundary separating organizational scopes is bypassed. Consequently, the application erroneously processes the read request for data residing outside the permitted execution context.\nThe attack flow proceeds as follows: 1) An authenticated user with legitimate read access to the root organization targets the GUI endpoint responsible for retrieving Stacked result sets. 2) The user crafts or submits a request directed at file paths or resources associated with child organizations stored within the datastore directory. 3) The vulnerable component fails to correctly match the request against the prefix deny list, treating the traversal or restricted path as valid. 4) The application reads and returns the requested result sets from the child organization to the root organization user.\nThe vulnerable component is the GUI handler responsible for parsing and validating paths to Stacked result sets against the prefix deny list. Authentication and privilege requirements mandate that the actor possess authenticated read access to the root organization, after which the flaw allows escalation of data visibility into child organizational contexts."
}