# CVE-2026-45061: Budibase: SSRF via trivial `.tar.gz` substring bypass in Plugin URL upload (`/api/plugin`)

> Attackers can bypass URL validation to perform Server-Side Request Forgery, potentially accessing internal resources if blacklist protections are disabled or bypassed.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-xh5j-727m-w6gg

## What is CVE-2026-45061?

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

### Official description

Budibase is an open-source low-code platform. Prior to 3.35.10, the Plugin URL upload endpoint (POST /api/plugin) validates the submitted URL with a single substring check: url.includes(".tar.gz"). Any URL containing .tar.gz anywhere in the string — in the path, query string, or fragment — passes this check. The URL then proceeds directly to fetchWithBlacklist() with no further validation of host, scheme, or path. Standalone, this vulnerability is blocked by Budibase's default SSRF blacklist, which covers private IP ranges. But the URL validation layer itself is broken regardless, and it directly enables SSRF in two realistic situations: (1) when chained with the BLACKLIST_IPS bypass ([001]), where the blacklist is empty; and (2) when the plugin server follows HTTP redirects from an external URL to an internal target (the default node-fetch behavior with redirect: 'follow'). This vulnerability is fixed in 3.35.10.

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

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

2 open source packages ship an affected version, including budibase.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `budibase` | npm | All versions | 3.35.10 |
| `budibase` | npm | All versions | 3.35.10 |

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

Upgrade budibase to 3.35.10 or later.

## Is CVE-2026-45061 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45061 is a high-severity server-side request forgery vulnerability in budibase, published on 27 May 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-45061 exists.

Affected packages and fixed versions:
- budibase (npm): affected all versions; fixed in 3.35.10
- budibase (npm): affected all versions; fixed in 3.35.10

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-45061/ (Markdown: https://insights.sbomify.com/CVE-2026-45061/index.md)
```

## Sources

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

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