CVE-2026-63758: SurrealDB versions before 3.1.0 contain an authorization bypass vulnerability in the KILL statement that allow

Q: How do I fix CVE-2026-63758?

surrealdb: upgrade to 3.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-63758 being exploited?

CVE-2026-63758 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-63758 affect?

CVE-2026-63758 affects surrealdb. Severity is medium (CVSS 5.4). SurrealDB versions before 3.1.0 contain an authorization bypass vulnerability in the KILL statement that allows authenticated database users to terminate other users' LIVE SELECT subscriptions. Attackers can issue KILL statements with targe

Q: How urgent is CVE-2026-63758?

Priority 25/100. No elevated risk signals yet.

Routine

MEDIUM 5.4UPGRADE

CVE-2026-63758 is a medium-severity flaw (CVSS 5.4) affecting surrealdb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SurrealDB versions before 3.1.0 contain an authorization bypass vulnerability in the KILL statement that allows authenticated database users to terminate other users' LIVE SELECT subscriptions. Attackers can issue KILL statements with target live query UUIDs to disrupt real-time data subscriptions of other users without ownership verification.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-862
Published	2026-07-20
Last modified	2026-07-22

Publisher (CNA): VulnCheck · Vendor: surrealdb

Last updated 2026-07-22 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-20 12:19 UTCPublished CVE record published
2026-07-22 15:10 UTCUpdated Record last modified

surrealdb surrealdb UPGRADE

Affected: < 3.1.0

Fixed in: 3.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy surrealdb || rpm -q surrealdb || surrealdb --version

2. UPGRADE to 3.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade surrealdb

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade surrealdb

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-63758?

surrealdb: upgrade to 3.1.0. Exact commands for each OS are on this page.

Is CVE-2026-63758 being exploited?

CVE-2026-63758 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-63758 affect?

CVE-2026-63758 affects surrealdb. Severity is medium (CVSS 5.4). SurrealDB versions before 3.1.0 contain an authorization bypass vulnerability in the KILL statement that allows authenticated database users to terminate other users' LIVE SELECT subscriptions. Attackers can issue KILL statements with targe

How urgent is CVE-2026-63758?

Priority 25/100. No elevated risk signals yet.

Related CVEs

CVE-2026-63734 MEDIUM 4.9 UPGRADE SurrealDB versions before 3.2.0 contain a denial of service vulnerability in the SurrealML header parser that
CVE-2026-63761 MEDIUM 4.3 UPGRADE SurrealDB before 3.1.0 silently substitutes the ES384 algorithm when a JWT access method is configured with AL
CVE-2026-63746 MEDIUM 6.5 UPGRADE SurrealDB versions before 3.1.0 fail to enforce table SELECT permissions when traversing graph edges or back-r
CVE-2026-63745 MEDIUM 5.4 UPGRADE SurrealDB versions before 3.1.0 contain an authorization bypass vulnerability where authenticated users can sp
CVE-2025-71390 HIGH 8.8 UPGRADE SurrealDB before 2.2.6, 2.3.6, and 2.1.8 (and 3.0.0-alpha.7 and earlier) fails to validate DNS-resolved hostna

References

← Back to latest CVEs