# CVE-2026-35216: Budibase: Unauthenticated Remote Code Execution via Webhook Trigger and Bash Automation Step

> Unauthenticated attackers can execute arbitrary commands as root via a public webhook triggering a Bash automation step in Budibase.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Apr 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-fcm4-4pj2-m5hf

## What is CVE-2026-35216?

CVE-2026-35216 is a critical command injection vulnerability in budibase, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Budibase is an open-source low-code platform. Prior to version 3.33.4, an unauthenticated attacker can achieve Remote Code Execution (RCE) on the Budibase server by triggering an automation that contains a Bash step via the public webhook endpoint. No authentication is required to trigger the exploit. The process executes as root inside the container. This issue has been patched in version 3.33.4.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

2 open source packages ship an affected version, including @budibase/server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@budibase/server` | npm | All versions | 3.33.4 |
| `@budibase/server` | npm | All versions | 3.33.4 |

Products: Budibase Budibase.

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

Upgrade @budibase/server to 3.33.4 or later.

## Is CVE-2026-35216 being exploited?

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

## Other vulnerabilities in budibase

- [CVE-2026-54350](https://insights.sbomify.com/CVE-2026-54350/): Budibase: Anonymous NoSQL operator injection via published-app query templates (critical 10.0)
- [CVE-2026-27702](https://insights.sbomify.com/CVE-2026-27702/): Budibase Vulnerable to Remote Code Execution via Unsafe eval() in View Filter Map Function (Budibase Cloud) (critical 9.9)
- [CVE-2026-54352](https://insights.sbomify.com/CVE-2026-54352/): Budibase: Arbitrary file read by workspace-builder via PWA-zip symlink upload (critical 9.6)
- [CVE-2026-31818](https://insights.sbomify.com/CVE-2026-31818/): Budibase: Server-Side Request Forgery via REST Connector with Empty Default Blacklist (critical 9.6)
- [CVE-2026-30240](https://insights.sbomify.com/CVE-2026-30240/): Budibase PWA ZIP Upload Path Traversal Allows Reading Arbitrary Server Files Including All Environment Secrets (critical 9.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35216 is a critical command injection vulnerability in budibase, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35216 exists.

Affected packages and fixed versions:
- @budibase/server (npm): affected all versions; fixed in 3.33.4
- @budibase/server (npm): affected all versions; fixed in 3.33.4

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

## Sources

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

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