SurrealDB before 3.1.0 contains an authorization bypass vulnerability in the RELATE statement that allows authenticated users with CREATE permission to overwrite existing edge records without UPDATE permission. Attackers can issue a RELATE statement with a SET id clause pointing to an existing edge id, causing the storage layer to silently overwrite the target record instead of rejecting the operation.
CVE-2026-63752
Score 4.3 from GitHub Security Advisory published 2026-07-20. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 6%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 20, 2026SurrealDB before 3.1.0 RELATE Statement Record Overwrite | Advisories | VulnCheck
https://www.vulncheck.com/advisories/surrealdb-before-relate-statement-record-overwrite`RELATE` overwrites existing edge records without `UPDATE` permission · Advisory · surrealdb/surrealdb · GitHub
https://github.com/surrealdb/surrealdb/security/advisories/GHSA-f82j-v89j-mf86Vendor Advisories for CVE-2026-63752(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 10:49 UTCEG score recompute
- 2026-07-26 10:49 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 23:41 UTCEG score recompute
- 2026-07-22 23:41 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 12:38 UTCEG score recompute
- 2026-07-20 12:38 UTCGHSA enrichment
- 2026-07-20 12:18 UTCEG score recompute
- 2026-07-20 12:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-285
Frequently asked(5)
What is CVE-2026-63752?
When was CVE-2026-63752 disclosed?
Is CVE-2026-63752 actively exploited?
What is the CVSS score of CVE-2026-63752?
How do I remediate CVE-2026-63752?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63752
Is Your Infrastructure Affected by CVE-2026-63752?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.