Velociraptor: Low-priv analyst reads arbitrary server files via ungated sql() VQL plugin
- Exploited
- No known exploitation
- Fix
- Fixed in 0.77.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.77.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Velociraptor, a tool for collecting host state information, lets a remote attacker with a low-privilege analyst account read arbitrary files on the server, including root-readable files when the server runs as root. The attacker reaches it over the network with low-privilege login and no user interaction, by abusing the unchecked `sql()` plugin to make outbound database connections to a rogue MySQL server that requests local files.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Velociraptor is a tool for collecting host-based state information using Velociraptor Query Language (VQL) queries. Prior to 0.77.2, SQLPlugin.Call in vql/parsers/sql/sql.go does not enforce plugin-level FILESYSTEM_READ or NETWORK checks before the mysql and postgres branches pass a caller-controlled connstring to sql.Open, allowing arbitrary outbound database connections. With attacker-controlled MySQL connection options that enable local-infile access, a rogue MySQL server can request files readable by the Velociraptor server process, including root-readable files when that process runs as root. The SQLite file accessor still enforces FILESYSTEM_READ, but a low-privilege analyst with ANY_QUERY can use the zero-permission data accessor and ATTACH DATABASE to create files without the plugin-level check. This issue is fixed in version 0.77.2.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.77.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Velocidex velociraptor
fixed in 0.77.2
Evidence 5
- Advisory
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-85737
Is CVE-2026-85737 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-85737?
velociraptor: before 0.77.2.Source: cve.now feed data
How do I fix CVE-2026-85737?
Upgrade to a fixed version: 0.77.2.Source: cve.now feed data