# CVE-2026-72855: Budibase before 3.40.0 DNS Rebinding SSRF via OpenAPI and REST

> Authenticated users can bypass DNS pinning via rebinding to access internal services, requiring an upgrade to Budibase.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/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-9x7q-v2pf-x72v, GHSA-xg5g-26x8-cvf4

## What is CVE-2026-72855?

CVE-2026-72855 is a high-severity server-side request forgery 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 server-side request forgery vulnerabilities in OpenAPI query import and REST query execution that allow authenticated builder-level users to bypass DNS pinning protections through DNS rebinding attacks. Attackers can configure hostnames that resolve to public addresses during validation but resolve to loopback or private addresses during actual connection, allowing access to blocked internal HTTP services.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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

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

## Is CVE-2026-72855 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72855 is a high-severity server-side request forgery 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-72855 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-72855/ (Markdown: https://insights.sbomify.com/CVE-2026-72855/index.md)
```

## Sources

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

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