# CVE-2026-15371: Velociraptor Stored XSS in URL column types

> Attackers can inject JavaScript via URL column types in Velociraptor's web GUI, leading to stored XSS and potential session hijacking.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-7wgv-gp5p-x4jc

## What is CVE-2026-15371?

CVE-2026-15371 is a high-severity cross-site scripting vulnerability in Rapid7 Velociraptor, published on 18 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### 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.

Weakness: CWE-177 (Improper Handling of URL Encoding (Hex Encoding))

## Which versions are affected by CVE-2026-15371?


## How do I fix CVE-2026-15371?

No fix has been published for CVE-2026-15371 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15371 being exploited?

There is no known exploitation of CVE-2026-15371 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15371 and fix it if it is affected.

What it is: CVE-2026-15371 is a high-severity cross-site scripting vulnerability in Rapid7 Velociraptor, published on 18 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-15371 in the wild and no public exploit code.

Affected product: Rapid7 Velociraptor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15371/ (Markdown: https://insights.sbomify.com/CVE-2026-15371/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15371
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15371
- OSV: https://osv.dev/vulnerability/CVE-2026-15371

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15371/
Summaries are generated and may contain mistakes; the official description above is the record.