SurrealDB has local file read of 2-column TSV files via analyzers

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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, SURREALFILEALLOWLIST , 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…

Published by the source

10 Apr 2025, 21:08 UTC

Last modified by the source

10 Apr 2025, 21:08 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2cvj-g5r5-jrrg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-2cvj-g5r5-jrrg

Advisory: SurrealDB has local file read of 2-column TSV files via analyzers
IDs: GHSA-2cvj-g5r5-jrrg
Record: https://patchnext.com/advisories/ghsa-2cvj-g5r5-jrrg (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: surrealdb 2.2.2, 2.1.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io surrealdb: affected >= 2.2.0, < 2.2.2; < 2.1.5; fixed in 2.1.5, 2.2.2

## Suggested inspection (read-only)
- crates.io surrealdb: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on surrealdb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2cvj-g5r5-jrrg (GitHub-reviewed advisory GHSA-2cvj-g5r5-jrrg lists affected ranges: crates.io surrealdb >=2.2.0 =0 <2.1.5)

Commands are suggestions: review each one before running it.