SurrealDB before 2.2.2 Local File Read via DEFINE ANALYZER
Impact
SurrealDB before 2.2.2 has a local file read vulnerability via the DEFINE ANALYZER statement, allowing authenticated users with certain privileges to read arbitrary files. Attackers can point analyzers to arbitrary file paths and exfiltrate content from two-column tab-separated files.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
surrealdb · VulnCheck
surrealdb
2 ranges
surrealdb · VulnCheck
surrealdb
Package identity
pkg:cargo/surrealdbExplore surrealdb →Identity supplied by VulnCheck. Version matching requires compatible range evidence.
Compare with this publisher’s ranges. This does not inspect your installation.
affected
2.2.0 → before 2.2.2
semver versions
unaffected
2.2.2
semver versions
Other versions: unaffected
surrealdb · VulnCheck
surrealdb
2 ranges
surrealdb · VulnCheck
surrealdb
Package identity
pkg:cargo/surrealdbExplore surrealdb →Identity supplied by VulnCheck. Version matching requires compatible range evidence.
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → before 2.1.5
semver versions
unaffected
2.1.5
semver versions
Other versions: unaffected
Original source description
SurrealDB versions before 2.2.2 contain a local file read vulnerability in the DEFINE ANALYZER statement that allows authenticated users to read arbitrary files on the file system. Attackers with root, namespace, or database level privileges can point analyzers to arbitrary file paths and exfiltrate content from two-column tab-separated files.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2025-71394View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Environment requirements
These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.
VulnCheck · platform conditions
Any condition may hold
Vulnerable product
cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:*From (inclusive): 2.2.0
Before: 2.2.2
Vulnerable product
cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:*Before: 2.1.5
Original applicability statements
[
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.2.2",
"versionStartIncluding": "2.2.0"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.1.5"
}
]
}
]
}
]Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.