Upstream information
Description
Velociraptor allows scheduling new collections via VQL queries in notebooks. For a user to schedule a new collection, they require the COLLECT_CLIENT permission. However, this is not enforced when the user can run a VQL query which resets the authorization provider.This allows a user who can run arbitrary VQL (usually with the "analyst" role) to launch new collections (usually requires the "investigator" role). This vulnerability is an escalation from an analyst to investigator role.
SUSE information
Overall state of this security issue: Pending
This issue is currently rated as having important severity.
| CVSS detail | CNA (cve@rapid7.com) | SUSE |
|---|---|---|
| Base Score | 8.2 | 8.2 |
| Vector | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N |
| Attack Vector | Network | Network |
| Attack Complexity | High | High |
| Privileges Required | Low | Low |
| User Interaction | None | None |
| Scope | Changed | Changed |
| Confidentiality Impact | High | High |
| Integrity Impact | High | High |
| Availability Impact | None | None |
| CVSSv3 Version | 3.1 | 3.1 |
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
| Product(s) | Source package | State |
|---|---|---|
| Products under general support and receiving all security fixes. | ||
| SUSE Linux Enterprise Server 16.0 | velociraptor | Affected |
| SUSE Linux Enterprise Server 16.1 | velociraptor | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | velociraptor | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | velociraptor | Affected |
| openSUSE Leap 16.0 | velociraptor | Affected |
SUSE Timeline for this CVE
CVE page created: Mon Aug 17 16:57:27 2026CVE page last modified: Tue Aug 18 11:49:37 2026