SurrealDB versions before 3.1.0 fail to validate DEFINE NAMESPACE or DEFINE DATABASE permissions when processing USE NS and USE DB statements. Unauthenticated attackers can create arbitrary namespaces and databases by issuing USE commands, bypassing authorization checks in the RPC use method and SurrealQL executor.
CVE-2026-63741
Score 6.5 from GitHub Security Advisory published 2026-07-20. a secondary CVSS source baseline 6.5; 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
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 34(Track)EG Risk 34/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 computedSeverity65% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 18.3%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 20, 2026SurrealDB before 3.1.0 Authentication Bypass via USE statement | Advisories | VulnCheck
https://www.vulncheck.com/advisories/surrealdb-before-authentication-bypass-via-use-statementUSE NS/DB implicit creation bypasses DEFINE authorization · Advisory · surrealdb/surrealdb · GitHub
https://github.com/surrealdb/surrealdb/security/advisories/GHSA-wp87-mgvq-5j93Vendor Advisories for CVE-2026-63741(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 13× in last 7d / 13× 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-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 23:43 UTCEG score recompute
- 2026-07-22 23:43 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:39 UTCEG score recompute
- 2026-07-20 12:39 UTCGHSA enrichment
- 2026-07-20 12:19 UTCEG score recompute
- 2026-07-20 12:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
Frequently asked(5)
What is CVE-2026-63741?
When was CVE-2026-63741 disclosed?
Is CVE-2026-63741 actively exploited?
What is the CVSS score of CVE-2026-63741?
How do I remediate CVE-2026-63741?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63741
Is Your Infrastructure Affected by CVE-2026-63741?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.