# CVE-2026-82241: Budibase backend-core SSRF via incomplete default blacklist


- **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
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-3fqg-454w-h447, GHSA-9754-4wm6-3c8r

## What is CVE-2026-82241?

CVE-2026-82241 is a high-severity vulnerability in budibase server, published on 28 Aug 2026. 

### Official description

Budibase backend-core (@budibase/backend-core, as used by @budibase/server) omits the shared address space range 100.64.0.0/10 from its default SSRF blacklist (DEFAULT_BLACKLIST) used by REST datasource query previews. When the default blacklist is active (i.e., a self-hosted deployment has not defined BLACKLIST_IPS), an authenticated user with the Builder permission can submit a REST datasource query preview request to POST /api/queries/preview targeting a reachable HTTP(S) service in the 100.64.0.0/10 range, causing the server to send a request to that target and return its response through the preview flow. Per the advisory, no released fix was identified at the time of publication; remediation is to add 100.64.0.0/10 to DEFAULT_BLACKLIST.

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

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


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

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

## Is CVE-2026-82241 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82241 is a high-severity vulnerability in budibase server, published on 28 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-82241 in the wild and no public exploit code.

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

## Sources

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

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