CVE-2026-18860
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.
Scoring
- Severity
- HIGH
- CVSS base score
- 8.7
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H
- EPSS probability
- 0.30%
- CWE
- CWE-280
- Published
- 2026-08-11
- Last modified
- 2026-08-11
Affected products
- Rapid7 Velociraptor
Weakness type
Related vulnerabilities
- CVE-2026-69907 — Windows Enterprise App Management Elevation of Privilege Vulnerability
- CVE-2026-55468 — Wagtail: Improper restriction handling on Pages admin API
- CVE-2026-59567 — Local privilege escalation
- CVE-2026-58416 — Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard)
- CVE-2026-73239 — Apache Allura: Missing permission checks IDOR
- CVE-2026-11804 — Program Module Vulnerability
- CVE-2026-62393 — Apache Kylin: Improper authorization in job information retrieval
- CVE-2026-45196 — GPU DDK - Arbitrary GPU register write in rgxfw_hwperf_hw due to unsanitized pointers from host kernel