CVE-2026-19072
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-19072 is a critical-severity Improper Neutralization of Internal Special Elements (CWE-164) vulnerability in Velociraptor (inferred from references). Its CVSS base score is 9.9 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-6 (Configuration Settings) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-85870
Vulnerability Data
Velociraptor stores the compiled VQL in the hunt object internally to avoid having to recompile the artifacts for each endpoint in the hunt. Although the field "compiled_collector_args" is an internal field, Velociraptor allowed the field to be set from a…
more
user API call. This allows another user who can schedule a hunt (minimal role of "investigator" ) to set the compiled VQL statements for the hunt bypassing any ACL checks that would normally be applied. This flaw can then be escalated to allow the "investigator" user to run arbitrary VQL statements as an administrator user on the Velociraptor server.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 5 OS baselines
V2.1.1
Mitigating Controls (NIST 800-53 r5) AI
Baseline configuration defines the approved production settings and prevents shipment while still in manufacturing or debug mode.
Establishing and enforcing the most restrictive configuration settings ensures the released product uses hardened production values.
Developer configuration management requires tracking and controlling the transition from manufacturing to release configuration.
Developer testing and evaluation can discover that the delivered build remains in a pre-production configuration.
Input validation directly requires checking and sanitizing special elements before they reach downstream components.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure development life cycle mandates input validation and sanitization that directly prevents improper neutralization of internal special elements.
Application security requirements explicitly call for controls against injection and malformed input that cause this weakness.
Secure system architecture principles reduce attack surface but do not specifically address neutralization of internal special elements.
Secure coding standards require proper escaping and neutralization of special elements, directly mitigating CWE-164.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248521 OL 8 must be a vendor-supported release. prevents CWE-1269
RHEL 7 (1 rule)
- V-204458 The Red Hat Enterprise Linux operating system must be a vendor supported release. prevents CWE-1269