Skip to main content
VulnerabilityPublished

CVE-2026-18860: Rapid7 Velociraptor · Improper handling of insufficient permissions or privileges

Affects Rapid7 VelociraptorSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 0.77.2 soon.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.77.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade Rapid7 Velociraptor to 0.77.2.

Affected software

ProductAffectedFixed in
Rapid7VelociraptorAffected
  • <0.77.2
Fixed in
  • 0.77.2
GitHubVelociraptorpkg:github/VelociraptorOther threatsAffected
  • <0.77.2
Fixed in
  • 0.77.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict child org administrators' ability to modify their ACL tokens or perform org deletion actions. Monitor for unusual deletion activities and apply principle of least privilege to org admin roles.

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.

References

Community reviews

Loading reviews…