dbcve.org
VelociraptorApplication · Rapid7

CVE-2026-7573

HIGH · 7.7 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 0.76.5 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
An authorization bypass (CWE-639) in the GetUserRoles gRPC API endpoint in Velocidex Velociraptor below version 0.76.5 allows any authenticated low-privilege user to retrieve the complete ACL policy (roles and permissions) for any user across all organizations by supplying targeted Name and Org parameters via a network request.

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 analysis · high confidence

An authorization bypass vulnerability (CWE-639) in the GetUserRoles gRPC API endpoint allows any authenticated low-privilege user to retrieve complete ACL policies (roles and permissions) for any user across all organizations by supplying targeted Name and Org parameters. This exposes sensitive access control information to unauthorized users.

MitigationUpgrade Velociraptor to version 0.76.5 or later to patch the authorization bypass in the GetUserRoles gRPC endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VelociraptorApplication
Affected:< 0.76.5

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Velociraptor installation
    Locate the Velociraptor server binary or service. Common paths include /opt/velociraptor, /usr/local/velociraptor, or check system services via 'systemctl list-units | grep velociraptor' or 'ps aux | grep velociraptor'. Also check for velociraptor-server process listening on common gRPC ports (8000, 8889).
    Affected if Velociraptor is installed and running as a server/service
  2. Determine installed Velociraptor version
    Run 'velociraptor --version' or check the binary version directly. If using a package manager, query via 'dpkg -l velociraptor' or 'rpm -qi velociraptor'. Compare the version number against 0.76.5.
    Affected if Installed version is below 0.76.5 (e.g., 0.76.4, 0.76.0, etc.)
  3. Verify gRPC API exposure
    Check network listeners for Velociraptor gRPC ports. Run 'netstat -tlnp | grep -E "(8000|8889)"' or 'ss -tlnp | grep velociraptor'. Review Velociraptor configuration files (typically velociraptor.yaml or velociraptor.conf) for bind_address and api_bind_port settings.
    Affected if gRPC API is bound to 0.0.0.0 or an accessible network interface rather than localhost only
  4. Review API access logs for GetUserRoles calls
    Examine Velociraptor audit logs or access logs for GetUserRoles gRPC API calls. Look for entries containing 'GetUserRoles' in the API method field. Check if low-privilege (non-admin) users are querying roles for other users or other organizations.
    Affected if Non-admin users are successfully calling GetUserRoles API for users outside their own organization

You are affected if Velociraptor version is below 0.76.5 AND the gRPC API is network-accessible to low-privilege users who can invoke GetUserRoles calls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 0.76.5 or later
Fixed in 0.76.5
Interim mitigation

Upgrade Velociraptor to version 0.76.5 or later to patch the authorization bypass in the GetUserRoles gRPC endpoint.

Recommended fix High confidence

Velociraptor 0.76.5

  1. 1. Back up your Velociraptor configuration and any custom policies.
  2. 2. Download Velociraptor version 0.76.5 or later from the official releases (docs.velociraptor.app or GitHub).
  3. 3. Verify the integrity of the downloaded package using published checksums.
  4. 4. Stop the Velociraptor service on all nodes.
  5. 5. Replace the Velociraptor binaries with the new version.
  6. 6. Restart the Velociraptor service.
  7. 7. Verify the service is running correctly and accessible.
  8. 8. As a best practice, confirm that the GetUserRoles endpoint now properly enforces authorization checks for low-privilege users.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Velociraptor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,460
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7573 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7573 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

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.

What belongs here
  • 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