Velociraptor Stored XSS in URL column types
Summary
| CVE | CVE-2026-15371 |
|---|---|
| State | PUBLISHED |
| Assigner | rapid7 |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-18 07:16:48 UTC |
| Updated | 2026-08-18 07:16:48 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 8.1 HIGH from [email protected]
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N
Problem Types: CWE-177 | CWE-177 CWE-177 Improper handling of URL encoding (hex encoding)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 8.1 | HIGH | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N |
| 3.1 | CNA | CVSS | 8.1 | HIGH | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
HighUser Interaction
RequiredScope
ChangedConfidentiality
HighIntegrity
HighAvailability
NoneCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Rapid7 | Velociraptor | affected 0.77.2 semver | Linux |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| docs.velociraptor.app/announcements/advisories/cve-2026-15371 | [email protected] | docs.velociraptor.app | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: yoojoon2 (https://github.com/yoojoon2) (en)
Additional Advisory Data
Workarounds
CNA: Users should not designate a column as type URL if the source of the table is untrusted (e.g. the results from artifact collections where the data is under the attacker's control).
There are currently no legacy QID mappings associated with this CVE.