# CVE-2026-109339: SurrealDB 3.1.0 before 3.3.0 Memory Exhaustion via Surrealism Module Output Buffering

> An attacker can crash the SurrealDB server by installing a malicious module that exhausts memory via unbounded output buffering.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-rj2f-8wx8-hgm5

## What is CVE-2026-109339?

CVE-2026-109339 is a medium-severity denial of service vulnerability in surrealdb, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SurrealDB 3.1.0 before 3.3.0 lets Surrealism modules exhaust server memory because module stdout/stderr lines are buffered unbounded in host memory, bypassing the configured module memory limit. An attacker can run an Owner-installed malicious module that writes output without newlines, crashing the server and denying service to all namespaces and databases.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-109339?


## How do I fix CVE-2026-109339?

No fix has been published for CVE-2026-109339 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109339 being exploited?

There is no known exploitation of CVE-2026-109339 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109339 and fix it if it is affected.

What it is: CVE-2026-109339 is a medium-severity denial of service vulnerability in surrealdb, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109339 in the wild and no public exploit code.

Affected product: surrealdb. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-109339/ (Markdown: https://insights.sbomify.com/CVE-2026-109339/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109339
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109339
- OSV: https://osv.dev/vulnerability/CVE-2026-109339

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109339/
Summaries are generated and may contain mistakes; the official description above is the record.