SurrealDB has an Authorization Bypass via Composite Record-id Paths

Exploitation

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

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-63745: 0.25% estimated exploitation activity in the next 30 days; percentile 16.35 (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.

An authenticated user could bypass permission rules that gated access on parts of a record's id — most commonly tenant-isolation rules of the form `PERMISSIONS FOR select WHERE id.tenant = $auth.id.tenant`. The same defect also let UNIQUE constraints defined on parts of an id admit duplicate entries. When a query referenced part of a composite record id (`id.tenant`, `id.uid`, …), SurrealDB read the value from the record's editable body fields instead of from the immutable id key. Because the body is editable but the id is fixed at creation, an attacker with write access could set the body field to any value and have permission checks read that spoofed value.

Impact What an attacker can do: - Read records hidden by permission rules of the form `id. = $auth. ` (typically tenant- or scope-isolation boundaries) by writing the same-named field on a record they control to the spoofed value. - Cause UNIQUE constraints defined on `id. ` to silently admit duplicate entries, leaving…

Published by the source

1 Jul 2026, 20:12 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-6vg3-hgrw-p5gf

2. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6vg3-hgrw-p5gf

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

# Patch Next advisory brief: CVE-2026-63745

Advisory: SurrealDB has an Authorization Bypass via Composite Record-id Paths
IDs: CVE-2026-63745, GHSA-6vg3-hgrw-p5gf
Record: https://patchnext.com/advisories/ghsa-6vg3-hgrw-p5gf (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: Medium (CVSS 5.4)
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.0. A vendor fix does not mean a deployment is fixed.

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

## 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-6vg3-hgrw-p5gf (GitHub-reviewed advisory GHSA-6vg3-hgrw-p5gf lists affected ranges: crates.io surrealdb >=0 <3.1.0)
- Verified: https://osv.dev/vulnerability/GHSA-6vg3-hgrw-p5gf (OSV record GHSA-6vg3-hgrw-p5gf lists affected ranges: crates.io surrealdb >=0 <3.1.0 (fixed))

Commands are suggestions: review each one before running it.