Velociraptor: Improper Handling of URL Encoding (Hex Encoding)
CVE-2026-15371 is a high-severity improper handling of URL encoding (hex encoding) vulnerability in Velociraptor from Rapid7, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, but only if a user takes part, for example by opening a link or file. The record lists version 0.77.2 as the first without the flaw, so updating Velociraptor to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.37% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Velociraptor to 0.77.2 or a later version.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Rapid7 | Velociraptor | before 0.77.2 | 0.77.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N. Scored by CNA (rapid7.com).
Official description
Velociraptor's web GUI allows specifying a custom type for columns in tables. The URL type takes the cell value and forms a URL which can be clicked in the GUI.The code does not limit the schemes allowed in this URL , allowing an attacker to specify a JavaScript scheme exposing the user to XSS.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Handling of URL Encoding (Hex Encoding)
The product does not properly handle when all or part of an input has been URL encoded.
How developers prevent this class of flaw
- Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
More Improper Handling of URL Encoding (Hex Encoding) vulnerabilities (CWE-177)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Velociraptor
- 9.9 Critical severity
- 7.7 High severity
- 9.9 Critical severity
- 8.9 High severity
- 8.2 High severity
- 7.1 High severity
Recent Improper Handling of URL Encoding (Hex Encoding) vulnerabilities
- 9.1 Critical severity
- 9.1 Critical severity
- 9.8 Critical severity
- 8.4 High severity
- 8.8 High severity
Spotted an error? Tell us.