Skip to content
Noroxi
CVE-2026-63751· NVD / CVE Program· CNA VulnCheck

SurrealDB before 3.1.0 Field Permission Bypass via JSON Patch

SurrealDB versions before 3.1.0 contain a field-level permission bypass vulnerability in JSON Patch operations that allows authenticated users to read protected fields. Attackers can use UPDATE PATCH with an empty from pointer in copy or move operations to duplicate all record fields, including those restricted by field-level SELECT permissions, into attacker-chosen destination fields.

MediumCVSS 5.3 · v4.0—No exploit Fix available
Published
Jul 20, 2026
Updated
Jul 28, 2026
EPSS
0.3% · 20th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · VulnCheck
5.3
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
surrealdbsurrealdb

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • surrealdb surrealdbbefore 3.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.

  • surrealdb surrealdb

    • 3.1.0not affected
    • before 3.1.0affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
crates.iosurrealdbbefore 3.1.03.1.0

Same product

surrealdb: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-71392SurrealDB before 2.2.2 SurrealQL Injection via export
    37Monitor
  • CVE-2026-63756SurrealDB before 3.1.0 Privilege Escalation via RPC Session Race Condition
    36Monitor
  • CVE-2024-58366SurrealDB before 1.1.1 Format String via Scripting Functions
    36Monitor
  • CVE-2026-102876SurrealDB before 3.3.0 Cross-Tenant Access via Headers
    34Monitor
  • CVE-2026-63760SurrealDB before 3.1.0 Denial of Service via JSON Parser
    34Monitor
  • CVE-2026-63757SurrealDB before 3.1.0 Session Hijacking via /rpc sessions
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
surrealdb surrealdb3.1.0Vendor (CNA)
crates.io:surrealdb3.1.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-637400 days apartSurrealDB before 3.1.4 Array Element Permission Bypass
    28Monitor
  • CVE-2026-637550 days apartSurrealDB before 3.1.0 Permission Bypass via WHERE Clause
    28Monitor
  • CVE-2025-713902 days apartSurrealDB before 2.3.6 deny-net Bypass via DNS Resolution
    23Monitor
  • CVE-2026-637330 days apartSurrealDB before 3.2.0 Permissions Bypass via PERMISSIONS Clause
    21Monitor
  • CVE-2026-637420 days apartSurrealDB before 3.1.0 Field Permission Bypass via Indexed COUNT
    21Monitor
  • CVE-2026-637490 days apartSurrealDB before 3.1.0 Authentication Bypass via LIVE SELECT
    21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

Weakness class (CWE)

CWE-863 · Incorrect Authorization

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records