# CVE-2026-73618: Budibase Server before 3.40.0 NoSQL Injection via JSON Parameter

> Attackers with query write permission can inject JSON characters to bypass filters and read, modify, or delete arbitrary MongoDB documents.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-qw6m-8fw2-2v64, GHSA-wg7g-xr7v-hf69

## What is CVE-2026-73618?

CVE-2026-73618 is a high-severity SQL injection vulnerability in budibase server, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Budibase Server before 3.40.0 contains a NoSQL injection vulnerability in the MongoDB query execution endpoint where user-supplied parameters are interpolated into JSON query templates without proper sanitization of JSON metacharacters. Attackers with query write permission can inject JSON structural characters to alter MongoDB queries, bypassing filters to read, modify, or delete arbitrary documents.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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

2 open source packages ship an affected version, including @budibase/server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@budibase/server` | npm | All versions to 3.38.1 | None |
| `@budibase/server` | npm | All versions to 3.38.1 | None |

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

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

## Is CVE-2026-73618 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73618 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73618 is a high-severity SQL injection vulnerability in budibase server, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73618 exists.

Affected packages and fixed versions:
- @budibase/server (npm): affected all versions up to 3.38.1; no fix listed
- @budibase/server (npm): affected all versions up to 3.38.1; no fix listed

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

## Sources

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

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