# CVE-2026-72853: Budibase before 3.40.0 SQL Injection via Oracle connector

> Attackers with write permissions can inject SQL via Oracle connector table names to read or modify arbitrary database data.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-mv4c-5rgh-72q9, GHSA-xj29-x47g-9w2c

## What is CVE-2026-72853?

CVE-2026-72853 is a high-severity SQL injection vulnerability in budibase, published on 13 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Budibase before 3.40.0 contains a SQL injection vulnerability in the Oracle datasource connector's post-write row lookup that fails to escape table names in identifiers. Attackers with write permission on a table with a double-quote in its name can inject SQL that executes as the datasource's database user to read or modify arbitrary data.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-72853 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72853 is a high-severity SQL injection vulnerability in budibase, published on 13 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72853 exists.

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

## Sources

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

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