CVE-2026-63763

HIGHNVD 8.87.5
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 5 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SurrealDB before 2.5.0 and before 3.0.0-beta.3 contains a confused deputy privilege escalation vulnerability. Unprivileged users (e.g., those with the database editor role) can create or modify fields containing futures, functions, or closures. Because these are executed in the context of the invoking/querying user rather than their creator, an attacker can plant malicious logic that executes with a higher-privileged user's permissions when that user reads or writes the affected record. This can lead to full privilege escalation, including creation of a root owner and server takeover.

CVSS v3
8.8
EG Score
7.5(low)
EPSS
15.0%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jul 20, 2026
Patch available. Sources: github.
generic

SurrealDB before 2.5.0 Privilege Escalation via Future Fields | Advisories | VulnCheck

https://www.vulncheck.com/advisories/surrealdb-before-privilege-escalation-via-future-fields
github Patch Available

Confused Deputy Privilege Escalation through Future Fields and Functions. · Advisory · surrealdb/surrealdb · GitHub

https://github.com/surrealdb/surrealdb/security/advisories/GHSA-3v2x-9xcv-2v2v

Vendor Advisories for CVE-2026-63763(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
surrealdb—2.5.0—

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.

  1. 2026-07-22 20:52 UTCNVD updateCVSS v3 → 8.8
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 16:41 UTCEG score recompute
  7. 2026-07-20 16:41 UTCGHSA enrichment
  8. 2026-07-20 16:05 UTCEG score recompute
  9. 2026-07-20 16:05 UTCGHSA enrichment
  10. 2026-07-20 12:37 UTCEG score recompute
  11. 2026-07-20 12:37 UTCGHSA enrichment
  12. 2026-07-20 12:18 UTCEG score recompute
  13. 2026-07-20 12:17 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63763?
CVE-2026-63763 is a high vulnerability published on July 20, 2026. SurrealDB before 2.5.0 and before 3.0.0-beta.3 contains a confused deputy privilege escalation vulnerability. Unprivileged users (e.g., those with the database editor role) can create or modify fields containing futures, functions, or closures. Because these are executed in the context of the…
When was CVE-2026-63763 disclosed?
CVE-2026-63763 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63763 actively exploited?
CVE-2026-63763 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-63763?
CVE-2026-63763 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.5. The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-63763?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63763, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63763

Explore →

Is Your Infrastructure Affected by CVE-2026-63763?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs