CVE-2026-18860: Velociraptor incorrect Org deletion permissions check
Published on 2026-07-31
Vulnogram
CVSS · HIGH · 8.7 ⁄10 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H
Scoring scenario:
GENERAL
attackVector:
NETWORK
attackComplexity:
LOW
privilegesRequired:
HIGH
userInteraction:
NONE
scope:
CHANGED
confidentialityImpact:
NONE
integrityImpact:
HIGH
availabilityImpact:
HIGH
Description
Velociraptor allows multi-tenant deployments named "Orgs".
By default Velociraptor, uses the ROOT org, but users can create child orgs for other tenants within the same deployment.
Users can have different permissions in each org. To manage Orgs, Velociraptor usually examines the ORG_ADMIN permission on the ROOT org.
This issue results from the Velociraptor server allowing for the deletion of Orgs by incorrectly checking the ORG_ADMIN permission of callers within the calling ORG instead of the ROOT org. However, Org admins of child orgs were able to add this permission to their ACL token within their own org. This allows an administrator in a child org, which is not also an administrator in the ROOT org, to delete other orgs.
Problem
CWE-280 Improper handling of insufficient permissions or privileges
Required configuration for exposure
This only affects deployments with untrusted SERVER_ADMIN users in child orgs who do not also have the SERVER_ADMIN permission in the ROOT org.
See the following documentation links:
- https://docs.velociraptor.app/docs/deployment/security/#managing-org-access
- https://docs.velociraptor.app/docs/deployment/orgs/#org-security
Workarounds
Ensure administrator users in child orgs are trusted to manage orgs.
| Product | Affected |
|---|---|
| Rapid7 Velociraptor on
Linux
source repo Default status is unaffected |
before 0.77.2 |
Credits
- Hamad Alghamdi