CVE-2026-19584 in Velociraptor
Summary
by MITRE • 09/10/2026
Velociraptor allows for the creation of notebook backups in its default enabled daily backup feature. When Velociraptor restores the backup, the notebook cell content is interpolated into a template with no ACL checks. This allows a malicious user with NOTEBOOK_EDITOR permission to plant a VQL query which will be evaluated at elevated permissions if the notebook's backup is subsequently restored.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 09/10/2026
The vulnerability in Velociraptor stems from an insecure handling of notebook backups during the restoration process, specifically affecting users who possess NOTEBOOK_EDITOR permissions. The system features a default-enabled daily backup mechanism that captures state data including user-created notebooks. When these backups are restored, the application reconstructs the notebook by interpolating cell content into a template structure without performing adequate access control list checks on the embedded code. This architectural flaw creates a privilege escalation vector where lower-privileged users can inject malicious VQL queries into their notebooks under the guise of standard editing activities.
From a technical perspective, the core issue is an injection vulnerability within the notebook restoration logic. Because the interpolation process does not validate whether the executing context has sufficient privileges to run specific commands, any code embedded in the backup file will be executed with elevated permissions when the restore operation completes. This effectively bypasses the intended security boundaries of the Velociraptor platform. A malicious actor who can edit notebooks can craft a VQL query designed to perform unauthorized actions such as data exfiltration, system modification, or further lateral movement within the monitored environment. The attack relies on social engineering or prior compromise to get an administrator or higher-privileged user to trigger the restoration of the compromised backup file.
The operational impact of this vulnerability is significant as it undermines the integrity and confidentiality guarantees provided by Velociraptor’s role-based access control model. An attacker with NOTEBOOK_EDITOR rights can achieve code execution at a much higher privilege level, potentially gaining full administrative control over the Velociraptor server or accessing sensitive forensic data collected from endpoints. This could lead to complete compromise of the incident response infrastructure, allowing the attacker to hide their tracks by modifying logs or disabling monitoring capabilities on targeted systems. The risk is exacerbated by the fact that backups are often managed by administrators who may not scrutinize every detail of restored content, assuming the backup process itself preserves security boundaries.
This vulnerability aligns with CWE-862 which describes missing authorization checks for critical functions and CWE-94 related to improper control of generation of code or commands. In terms of threat modeling, this behavior corresponds to ATT&CK technique T1053 Scheduled Task/Job where an attacker uses system mechanisms to execute malicious payloads persistently or on a schedule, although here the trigger is manual restoration rather than automated scheduling. It also reflects aspects of T1648 which involves access to cloud infrastructure APIs if applicable within the broader Velociraptor deployment context involving remote agents and centralized management.
Mitigation strategies should focus on immediate remediation through software updates provided by the vendor, ensuring that the latest version with patched restoration logic is deployed across all instances. Administrators must enforce strict validation of notebook content before initiating any restore operations from backups. Implementing a review process where changes to critical configurations or restored data are verified by multiple authorized personnel can reduce the risk of successful exploitation. Additionally, restricting NOTEBOOK_EDITOR permissions to only those users who absolutely require them and auditing their activities closely will limit the attack surface. Enabling detailed logging for backup restoration events allows security teams to detect anomalous patterns indicative of this abuse vector. Regularly rotating administrative credentials and monitoring for unusual VQL query executions can further enhance detection capabilities against such privilege escalation attempts.