The CVSS 6.8 rating for this Velociraptor bypass obscures a more fundamental problem: prefix-based path filtering was never appropriate as an isolation mechanism for multi-tenant VFS access, and this CVE proves why. The bypass allows a user with ROOT organization read permissions to access files in other organizations where they may have no legitimate access — a tenant isolation failure that exposes sensitive forensic data, incident response artifacts, and threat intelligence collected across your deployment. The prerequisite ROOT org access reduces but does not eliminate severity; many deployments treat ROOT org as a baseline administrative tier, making this a meaningful privilege escalation path in practice. The deeper concern is what the patch actually does. If Velociraptor simply adds more denied prefixes to the blocklist, you should treat this as a recurring vulnerability — each patch becomes a race against the next bypass variant. The correct fix moves VFS access control to capability-based gating that occurs before any path evaluation, making the prefix list irrelevant rather than essential. Your priority: determine whether your deployment runs in multi-tenant mode where cross-org isolation matters, audit which users hold ROOT org permissions, and verify whether the applied patch rearchitects the access model or just hardens the deny list. If it's the latter, treat this as a known architectural weakness requiring ongoing monitoring rather than a one-time fix.
CVE-2026-18636
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Velociraptor gRPC API has a VFSGetBuffer endpoint which allows reading files from the datastore. To prevent users from reading sensitive files or accessing other orgs, the requested path is prefix checked against a list of denied prefixes. This prefix check can be bypassed allowing a user to access usually denied files. If the user has read permission in the ROOT org, this allows access to other orgs, in which the user may not have permission.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA detailed technical summary for this CVE is being prepared.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,000. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-18636 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThe CVSS 6.8 rating for this Velociraptor bypass obscures a more fundamental problem: prefix-based path filtering was never appropriate as an isolation mechanism for multi-tenant VFS access, and this CVE proves why. The bypass allows a user with ROOT organization read permissions to access files in other organizations where they may have no legitimate access — a tenant isolation failure that exposes sensitive forensic data, incident response artifacts, and threat intelligence collected across your deployment. The prerequisite ROOT org access reduces but does not eliminate severity; many deployments treat ROOT org as a baseline administrative tier, making this a meaningful privilege escalation path in practice. The deeper concern is what the patch actually does. If Velociraptor simply adds more denied prefixes to the blocklist, you should treat this as a recurring vulnerability — each patch becomes a race against the next bypass variant. The correct fix moves VFS access control to capability-based gating that occurs before any path evaluation, making the prefix list irrelevant rather than essential. Your priority: determine whether your deployment runs in multi-tenant mode where cross-org isolation matters, audit which users hold ROOT org permissions, and verify whether the applied patch rearchitects the access model or just hardens the deny list. If it's the latter, treat this as a known architectural weakness requiring ongoing monitoring rather than a one-time fix.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-18636 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data