CVE-2026-18860: Velociraptor incorrect Org deletion permissions check
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 ORGADMIN permission on the ROOT org.
This issue results from the Velociraptor server allowing for the deletion of Orgs by incorrectly checking the ORGADMIN 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-18860?
The severity of CVE-2026-18860 is high, rated at 8.7.
How do I fix CVE-2026-18860?
To fix CVE-2026-18860, ensure that proper permissions are in place for managing Org deletions in Velociraptor.
What does CVE-2026-18860 affect?
CVE-2026-18860 affects the permissions checks related to Org deletions in multi-tenant deployments of Velociraptor.
Who is impacted by CVE-2026-18860?
Users with improper Org deletion permissions may be impacted by CVE-2026-18860, leading to potential data exposure or loss.
What is the risk associated with CVE-2026-18860?
CVE-2026-18860 has a risk score of 59, indicating a significant potential impact due to permission misconfigurations.