How severe is GHSA-2cvj-g5r5-jrrg?

No CVSS score has been assigned to GHSA-2cvj-g5r5-jrrg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2cvj-g5r5-jrrg?

GHSA-2cvj-g5r5-jrrg affects the following packages: surrealdb (crates.io), surrealdb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-2cvj-g5r5-jrrg?

Update surrealdb to 2.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2cvj-g5r5-jrrg is resolved across your whole dependency graph.

How do I detect GHSA-2cvj-g5r5-jrrg in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for surrealdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2cvj-g5r5-jrrg if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-2cvj-g5r5-jrrg actively exploited in the wild?

No public exploit code has been indexed for GHSA-2cvj-g5r5-jrrg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2cvj-g5r5-jrrg?

GHSA-2cvj-g5r5-jrrg has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2cvj-g5r5-jrrg?

GHSA-2cvj-g5r5-jrrg is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-2cvj-g5r5-jrrg published, and has it been updated?

GHSA-2cvj-g5r5-jrrg was published on April 10, 2025 and was last updated on July 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

SurrealDB has local file read of 2-column TSV files via analyzersGHSA-2cvj-g5r5-jrrg

Fix: surrealdb/surrealdb#5600

GHSA-2cvj-g5r5-jrrg is a Path Traversal vulnerability in surrealdb. A fix is available for surrealdb — see the affected versions and patch details below.

Also known asCVE-2025-71394

Published

Apr 10, 2025

Updated

Jul 19, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2cvj-g5r5-jrrg.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🦀surrealdb🦀surrealdb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

An authenticated system user at the root, namespace, or database levels can use the DEFINE ANALYZER statement to point to arbitrary file locations on the file system, and should the file be tab separated with two columns, the analyzer can be leveraged to exfiltrate the content.

This issue was discovered and patched during an code audit and penetration test of SurrealDB by cure53, the severity defined within cure53's preliminary finding is Low, matched by our CVSS v4 assessment.

Impact

Limited to unauthorised access to 2 column TSV files on the file system

Patches

A patch has been created that introduces a new environment variable, SURREAL_FILE_ALLOWLIST , which contains a list of allowed file paths. When a mapping file is processed, the mapper checks if the file’s path is within one of the allowed paths.

Versions 2.1.5, 2.2.2 and later are not affected by this issue.

Workarounds

Users unable to update may want to limit those with root, namespace, or database level users to trusted parties only.

References

SurrealQL Documentation - DEFINE ANALYZER #5600

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`surrealdb`	≥ 2.2.0&&< 2.2.2	2.2.2`cargo update -p surrealdb --precise 2.2.2`
🦀crates.io	`surrealdb`	all versions	2.1.5`cargo update -p surrealdb --precise 2.1.5`

Affected Products

1 product · 2 configurations

Application

surrealdbsurrealdb

≥ 2.2.0 && < 2.2.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for surrealdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update surrealdb to 2.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2cvj-g5r5-jrrg is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

An authenticated system user at the root, namespace, or database levels can use the `DEFINE ANALYZER` statement to point to arbitrary file locations on the file system, and should the file be tab separated with two columns, the analyzer can be leveraged to exfiltrate the content. This issue was discovered and patched during an code audit and penetration test of SurrealDB by cure53, the severity defined within cure53's preliminary finding is Low, matched by our CVSS v4 assessment. ### Impact Limited to unauthorised access to 2 column TSV files on the file system ### Patches A patch has been

O3 Security · Impact-Aware SCA

Is GHSA-2cvj-g5r5-jrrg in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works