CVE-2026-63750

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-20) is not newer than that change (2026-07-28), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-45921 (ENISA EUVD) · GHSA-qg3v-r4m7-x5f5 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists surrealdb versions before 3.1.0 as affected, and surrealdb versions 3.1.0 as unaffected. No release containing a fix is confirmed on record.

SurrealDB versions before 3.1.0 fail to apply the SURREAL_WEBSOCKET_MAX_MESSAGE_SIZE limit to anonymous /sql WebSocket connections, allowing attackers to buffer unbounded frames in the per-connection read buffer. Attackers can stream WebSocket frames larger than the configured limit across multiple concurrent connections to consume excessive memory and degrade /sql availability.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 20, 2026

Last Modified

July 28, 2026

Advisory Details (2)

Auto-updated Jul 20, 2026
No fix on record yet. Sources: github.
Web page

SurrealDB before 3.1.0 Memory Amplification via /sql WebSocket | Advisories | VulnCheck

https://www.vulncheck.com/advisories/surrealdb-before-memory-amplification-via-sql-websocket
GitHub advisoryMentions a patch (unverified)

Pre-auth memory amplification via unbounded `/sql` WebSocket frames · Advisory · surrealdb/surrealdb · GitHub

https://github.com/surrealdb/surrealdb/security/advisories/GHSA-65rj-r9fh-jp2v

Vendor Advisories for CVE-2026-63750(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 8× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 244 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 144 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-10-25 14:13 UTCEG score recompute
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-20 09:16 UTCEG score recompute
  10. 2026-10-20 09:16 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  11. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-18 03:23 UTCEG score recompute
  14. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-13 11:55 UTCEG score recompute
  20. 2026-10-13 11:55 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  21. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-12 15:48 UTCEG score recompute
  23. 2026-10-11 19:33 UTCEG score recompute
  24. 2026-10-11 16:48 UTCEG score recompute
  25. 2026-10-11 14:10 UTCEG score recompute
Show 75 more
  1. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-04 14:57 UTCEG score recompute
  10. 2026-10-04 14:57 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  11. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-01 07:46 UTCEG score recompute
  15. 2026-10-01 07:46 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  16. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-09-28 06:26 UTCEG score recompute
  19. 2026-09-28 06:26 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  20. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-09-24 03:30 UTCEG score recompute
  22. 2026-09-24 03:30 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  23. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-09-23 01:44 UTCEG score recompute
  25. 2026-09-23 01:44 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  26. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  27. 2026-09-18 03:59 UTCEG score recompute
  28. 2026-09-18 03:59 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  29. 2026-09-17 05:15 UTCEG score recompute
  30. 2026-09-17 05:15 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  31. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  32. 2026-09-16 12:49 UTCEG score recompute
  33. 2026-09-16 12:49 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  34. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-09-14 03:54 UTCEG score recompute
  36. 2026-09-14 03:54 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  37. 2026-09-13 16:02 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  38. 2026-09-13 03:20 UTCEG score recompute
  39. 2026-09-13 03:20 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  40. 2026-09-12 10:03 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  41. 2026-09-11 21:31 UTCEG score recompute
  42. 2026-09-11 21:31 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  43. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  44. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  45. 2026-09-11 09:32 UTCEG score recompute
  46. 2026-09-11 09:32 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  47. 2026-09-09 12:02 UTCEG score recompute
  48. 2026-09-09 12:02 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  49. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  50. 2026-09-07 22:59 UTCEG score recompute
  51. 2026-09-07 22:59 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  52. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  53. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  54. 2026-09-06 11:49 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  55. 2026-09-05 21:28 UTCEG score recompute
  56. 2026-09-05 21:28 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  57. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  58. 2026-09-05 09:36 UTCEG score recompute
  59. 2026-09-05 09:36 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  60. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  61. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  62. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  63. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  64. 2026-08-31 03:26 UTCEG score recompute
  65. 2026-08-31 03:26 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  66. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  67. 2026-08-30 15:32 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  68. 2026-08-30 02:40 UTCEG score recompute
  69. 2026-08-30 02:40 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  70. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  71. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  72. 2026-08-27 23:47 UTCEG score recompute
  73. 2026-08-27 23:47 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3
  74. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  75. 2026-08-27 11:44 UTCGHSA enrichmentGHSA-qg3v-r4m7-x5f5 · GitHub CVSS 5.3

Frequently asked(5)

What is CVE-2026-63750?
CVE-2026-63750 is a high-severity vulnerability; its CVE record was published on July 20, 2026. SurrealDB versions before 3.1.0 fail to apply the SURREALWEBSOCKETMAXMESSAGESIZE limit to anonymous /sql WebSocket connections, allowing attackers to buffer unbounded frames in the per-connection read buffer. Attackers can stream WebSocket frames larger than the configured limit across multiple…
When was CVE-2026-63750 made public?
CVE-2026-63750 was made public on May 27, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 20, 2026. EchelonGraph's copy of the record carries a last-modified date of July 28, 2026; the record at its source may have been updated since.
Is CVE-2026-63750 actively exploited?
CVE-2026-63750 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63750?
CVE-2026-63750 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-63750?
No fix for CVE-2026-63750 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists surrealdb versions before 3.1.0 as affected, and surrealdb versions 3.1.0 as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-63750 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63750

Explore →

Is Your Infrastructure Affected by CVE-2026-63750?

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