Skip to main content
Menu
CVEs

SurrealDB denial of service via decimal overflow in math::sum

CVE-2026-134302Published November 21, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.0.0
Who is exposed
Specific setups only

Summary

SurrealDB 1.0.0 before 4.0.0 contains a denial of service vulnerability that allows any user able to run queries to crash the server by triggering unchecked decimal overflow in math::sum or math::product. Attackers can submit a query summing or multiplying large decimal literals or aggregate stored decimals with GROUP ALL, causing a rust_decimal panic that terminates the entire server process.

Who should check

Teams running SurrealDB before 4.0.0, especially where any user can run queries using math::sum or math::product on decimal data.

“Affecting surrealdb >= 1.0.0, < 4.0.0”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    SurrealDB versions from 1.0.0 before 4.0.0. A query must sum or multiply decimal values, such as large decimal literals, or aggregate stored decimals with GROUP ALL.
  2. Upgrade to a fixed version: 4.0.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134302 (SurrealDB 1.0.0 before 4.0.0 DoS via Decimal Overflow in math::sum and math::product), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134302 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: from 1.0.0, fixed in 4.0.0
Fixed versions: 4.0.0.
Conditions (all must be true for the bug to be hit):
- SurrealDB versions from 1.0.0 before 4.0.0. (source: https://www.vulncheck.com/advisories/surrealdb-1.0.0-before-4.0.0-dos-via-decimal-overflow-in-math-sum-and-math-product)
- A query must sum or multiply decimal values, such as large decimal literals, or aggregate stored decimals with GROUP ALL. (source: https://www.vulncheck.com/advisories/surrealdb-1.0.0-before-4.0.0-dos-via-decimal-overflow-in-math-sum-and-math-product)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134302 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134302 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-g422-fj9r-m92g
- https://www.vulncheck.com/advisories/surrealdb-1.0.0-before-4.0.0-dos-via-decimal-overflow-in-math-sum-and-math-product
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134302
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134302"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects crates.io packages
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · surrealdb/surrealdb · Advisory GHSA-g422-fj9r-m92g
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134302
RecordNVD · CVE-2026-134302
Other links 1
Linkvulncheck.com · advisories/surrealdb-1.0.0-before-4.0.0-dos-via-decimal-overflow-in-math-sum-and-math-product

Questions about CVE-2026-134302

Is CVE-2026-134302 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A query that sums or multiplies large decimal values, such as large decimal literals, or that aggregates stored decimals with GROUP ALL can make the whole SurrealDB server process exit. All connections, databases and namespaces on that instance then lose service.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134302?

surrealdb (crates.io): from 1.0.0 before 4.0.0.

Source: cve.now feed data

Am I affected, and how do I check?

SurrealDB versions from 1.0.0 up to but not including 4.0.0 are in the affected range, so compare the installed SurrealDB version against that range. Exposure also depends on whether queries call math::sum or math::product on decimal values, or use GROUP ALL over stored decimals.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134302?

The affected range ends before 4.0.0, so 4.0.0 is the first version outside it. The checked facts do not name a separate patch identifier or a workaround.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.