CVE-2024-58364: SurrealDB versions before 1.2.1 contain an uncaught exception handling vulnerability in span rendering when pa

Q: How do I fix CVE-2024-58364?

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

Q: Is CVE-2024-58364 being exploited?

CVE-2024-58364 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-2024-58364 affect?

CVE-2024-58364 affects surrealdb. Severity is medium (CVSS 6.5). SurrealDB versions before 1.2.1 contain an uncaught exception handling vulnerability in span rendering when parsing queries with errors on line terminator characters. Authorized clients can submit malformed queries that trigger a panic in t

Q: How urgent is CVE-2024-58364?

Priority 32/100. No elevated risk signals yet.

Routine

MEDIUM 6.5UPGRADE

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

SurrealDB versions before 1.2.1 contain an uncaught exception handling vulnerability in span rendering when parsing queries with errors on line terminator characters. Authorized clients can submit malformed queries that trigger a panic in the span rendering code, crashing the server and causing denial of service.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 61%)
CISA exploited list	No
Weakness	CWE-248
Published	2026-07-18
Last modified	2026-08-12

Publisher (CNA): VulnCheck · Vendor: surrealdb

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

Am I affected?

Timeline

2026-07-18 14:17 UTCPublished CVE record published
2026-08-12 18:12 UTCUpdated Record last modified

surrealdb surrealdb UPGRADE

Affected: < 1.2.1

Fixed in: 1.2.1

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 1.2.1 (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-2024-58364?

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

Is CVE-2024-58364 being exploited?

CVE-2024-58364 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-2024-58364 affect?

CVE-2024-58364 affects surrealdb. Severity is medium (CVSS 6.5). SurrealDB versions before 1.2.1 contain an uncaught exception handling vulnerability in span rendering when parsing queries with errors on line terminator characters. Authorized clients can submit malformed queries that trigger a panic in t

How urgent is CVE-2024-58364?

Priority 32/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