CVE-2025-71393: SurrealDB before 2.2.2 with scripting enabled fails to properly enforce recursion limits when native functions

Routine

MEDIUM 6.5UPGRADE

CVE-2025-71393 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 before 2.2.2 with scripting enabled fails to properly enforce recursion limits when native functions contain embedded JavaScript that issues new queries. Authenticated attackers can bypass the recursion limit by chaining native and JavaScript function calls to trigger infinite recursion and exhaust server memory.

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.5% (top 60%)
CISA exploited list	No
Weakness	CWE-674
Published	2026-07-18
Last modified	2026-09-29

Publisher (CNA): VulnCheck · Vendor: surrealdb

Last updated 2026-09-29 · 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-09-29 19:10 UTCUpdated Record last modified

surrealdb surrealdb UPGRADE

Affected: < 2.0.5 · >= 2.1.0 and < 2.1.5 · >= 2.2.0 and < 2.2.2

Fixed in: 2.0.5, 2.1.5, 2.2.2

Safe to downgrade to: a release before 2.1.0

1. Check installed version

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

2. UPGRADE to 2.0.5 (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.

3. If no update is available yet, DOWNGRADE to a release before 2.1.0 (Debian / Ubuntu)

apt-cache madison surrealdb sudo apt install surrealdb=<VERSION_BEFORE_2.1.0> sudo apt-mark hold surrealdb

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list surrealdb sudo dnf downgrade surrealdb-<VERSION_BEFORE_2.1.0> sudo dnf versionlock add surrealdb

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2025-71393?

surrealdb: upgrade to 2.0.5, 2.1.5, 2.2.2. Exact commands for each OS are on this page.

Is CVE-2025-71393 being exploited?

CVE-2025-71393 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-2025-71393 affect?

CVE-2025-71393 affects surrealdb. Severity is medium (CVSS 6.5). SurrealDB before 2.2.2 with scripting enabled fails to properly enforce recursion limits when native functions contain embedded JavaScript that issues new queries. Authenticated attackers can bypass the recursion limit by chaining native an

How urgent is CVE-2025-71393?

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