# CVE-2026-72857: Budibase before 3.40.0 Credential Exposure via STRING Fields

> Authenticated users can read plaintext database credentials and service keys from STRING fields, exposing backend infrastructure secrets.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/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:** 14 Aug 2026
- **Also known as:** GHSA-6mpp-gfg5-x2vv, GHSA-95j2-62cr-h4p5

## What is CVE-2026-72857?

CVE-2026-72857 is a high-severity vulnerability in budibase, 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 fails to redact datasource credentials stored in STRING typed fields, allowing authenticated users to read MongoDB connection strings and Firebase private keys in plaintext. Attackers with table read permissions can retrieve datasource configurations through the read API to obtain live backend database credentials and service account keys.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-72857 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72857 is a high-severity vulnerability in budibase, 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-72857 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-72857/ (Markdown: https://insights.sbomify.com/CVE-2026-72857/index.md)
```

## Sources

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

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