# CVE-2026-103757: Budibase before 3.41.0 SSRF via uploadUrl in AI Table Generation

> Authenticated users can trigger server-side requests to internal URLs via AI table generation, potentially exposing sensitive cloud metadata credentials.

- **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:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-2524-3r74-44wr, GHSA-3c52-v5v2-3r56

## What is CVE-2026-103757?

CVE-2026-103757 is a high-severity server-side request forgery vulnerability in budibase, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Budibase through 3.41.0 contains a server-side request forgery vulnerability in AI table generation because the uploadUrl function in packages/server/src/utilities/fileUtils.ts uses raw node-fetch instead of fetchWithBlacklist. Authenticated builder users can send a prompt to POST /api/ai/tables that places an internal URL in an attachment column, causing the server to fetch it and return a presigned object-storage URL containing the response, such as cloud metadata credentials.

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

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


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

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

## Is CVE-2026-103757 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103757 is a high-severity server-side request forgery vulnerability in budibase, published on 1 Oct 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-103757 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-103757/ (Markdown: https://insights.sbomify.com/CVE-2026-103757/index.md)
```

## Sources

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

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