SurrealDB: Arbitrary file read via DEFINE ANALYZER mapper() filter

Exploitation

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

CVSS

7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2026-63739: 0.48% estimated exploitation activity in the next 30 days; percentile 41.15 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

SurrealDB's full-text search lets you define a text analyzer whose `mapper` filter loads a term-mapping file from disk (`DEFINE ANALYZER ... FILTERS mapper(' ')`). A database user with the `EDITOR` or `OWNER` role could point that filter at any file the SurrealDB process can read and have its content returned in the query's error message. File access is meant to be restricted by the `SURREAL_FILE_ALLOWLIST` setting, but an empty allowlist applied no restriction at all — and empty is the default.

Impact The file is read with the privileges of the SurrealDB process, so a database `EDITOR` or `OWNER` user can disclose the contents of any file the process can access. Only the first line of the file is returned, except for files with no newlines. However recovering the process's command line and environment could expose startup root credentials (`--user` / `--pass`) and secret environment variables, escalating a single-database role toward full control of the instance. The read on…

Published by the source

19 Jun 2026, 22:10 UTC

Last modified by the source

4 Nov 2026, 02:56 UTC

Source last checked

4 Nov 2026, 06:30 UTC

1. Revision 2 · amended · 4 Nov 2026

   Amended from osv record GHSA-cc8f-fcx3-gpjr

2. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cc8f-fcx3-gpjr

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

# Patch Next advisory brief: CVE-2026-63739

Advisory: SurrealDB: Arbitrary file read via DEFINE ANALYZER mapper() filter
IDs: CVE-2026-63739, GHSA-cc8f-fcx3-gpjr
Record: https://patchnext.com/advisories/ghsa-cc8f-fcx3-gpjr (revision 2, source checked 4 Nov 2026, 06:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: surrealdb 3.1.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io surrealdb: affected < 3.1.5; fixed in 3.1.5

## 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-cc8f-fcx3-gpjr (GitHub-reviewed advisory GHSA-cc8f-fcx3-gpjr lists affected ranges: crates.io surrealdb >=0 <3.1.5)
- Verified: https://osv.dev/vulnerability/GHSA-cc8f-fcx3-gpjr (OSV record GHSA-cc8f-fcx3-gpjr lists affected ranges: crates.io surrealdb >=0 <3.1.5 (fixed))

Commands are suggestions: review each one before running it.