# CVE-2026-73617: Budibase before 3.40.0 NoSQL Injection via MongoDB datasource

> Attackers can inject MongoDB operators to bypass access controls, read data, modify collections, or execute JavaScript in Budibase applications.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/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-pmpg-2mxq-6xwr, GHSA-rqxq-f5cc-3xp6

## What is CVE-2026-73617?

CVE-2026-73617 is a high-severity code 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 before 3.40.0 contains a NoSQL injection vulnerability in the MongoDB datasource integration where user-supplied parameters are enriched with handlebars using noEscaping: true and parsed without operator filtering. Attackers can inject MongoDB operators through query parameters to bypass per-user access controls, read arbitrary documents, execute JavaScript via $where operators, or modify collections through update and delete operations.

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

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

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-73617?

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

## Is CVE-2026-73617 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73617 is a high-severity code 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: There is no known exploitation of CVE-2026-73617 in the wild and no public exploit code.

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

## Sources

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

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