# GHSA-q8qp-67f9-wr3f: SurrealDB vulnerable to Denial of Service due to nested types annotations

> An authenticated attacker can crash the SurrealDB server by sending queries with deeply nested type annotations, exhausting memory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jul 2026

## What is GHSA-q8qp-67f9-wr3f?

GHSA-q8qp-67f9-wr3f is a denial of service vulnerability in surrealdb, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The SurrealDB type/kind parser did not enforce the configured recursion depth limit when parsing nested type annotations. The expression parser already enforced the limit for analogous constructs; the kind parser omitted it. An authenticated attacker could send a query with deeply nested type annotations (e.g., `array<option<array<option<...>>>>`) and exhaust server memory, crashing the process.

This is an incomplete fix for [GHSA-6r8p-hpg7-825g](https://github.com/surrealdb/surrealdb/security/advisories/GHSA-6r8p-hpg7-825g), which addressed the same class of bug in the expression parser but did not cover the kind/type annotation parser code path.

### Impact

An authenticated user with query execution privileges can crash a SurrealDB server with a single WebSocket message containing deeply nested type annotations.

### Patches

A patch has been introduced that wraps `parse_concrete_kind` and the `OPTION<...>` arm of `parse_inner_kind` with `enter_object_recursion!`, bounding the recursive cycle `parse_concrete_kind → parse_inner_kind → parse_inner_single_kind → parse_concrete_kind` at the configured `object_recursion_limit` (default 100). Regression tests cover both cast and `DEFINE FIELD` paths.

- Versions 3.1.0 and later are not affected by this issue.

### Workarounds

Restrict the ability of untrusted users to execute arbitrary queries via the `--deny-arbitrary-query` capability flag for the affected user classes (guest, record, or system). Disabling untrusted access to the WebSocket `/rpc` endpoint also prevents exploitation; the HTTP `/sql` endpoint's 1 MiB body limit constrains nesting to a depth where OOM is not feasible.

## Which versions are affected by GHSA-q8qp-67f9-wr3f?

2 open source packages ship an affected version, including surrealdb.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `surrealdb` | crates.io | All versions | 3.1.0 |
| `surrealdb` | crates.io | All versions | 3.1.0 |

## How do I fix GHSA-q8qp-67f9-wr3f?

Upgrade surrealdb to 3.1.0 or later.

## Is GHSA-q8qp-67f9-wr3f being exploited?

There is no known exploitation of GHSA-q8qp-67f9-wr3f in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-q8qp-67f9-wr3f and fix it if it is affected.

What it is: GHSA-q8qp-67f9-wr3f is a denial of service vulnerability in surrealdb, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-q8qp-67f9-wr3f in the wild and no public exploit code.

Affected packages and fixed versions:
- surrealdb (crates.io): affected all versions; fixed in 3.1.0
- surrealdb (crates.io): affected all versions; fixed in 3.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-q8qp-67f9-wr3f/ (Markdown: https://insights.sbomify.com/GHSA-q8qp-67f9-wr3f/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-q8qp-67f9-wr3f

---
From sbomify Insights: https://insights.sbomify.com/GHSA-q8qp-67f9-wr3f/
Summaries are generated and may contain mistakes; the official description above is the record.
