# CVE-2026-100682: Budibase Server before 3.45.0 Arbitrary File Write via ZIP Symlink

> Attackers with BUILDER role can write arbitrary files as root via malicious ZIP symlinks, enabling remote code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/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:** 26 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-37r6-5jxh-vm83, GHSA-xphc-jppf-jrhm

## What is CVE-2026-100682?

CVE-2026-100682 is a high-severity path traversal vulnerability in budibase server, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Budibase Server before 3.45.0 contains an arbitrary file write vulnerability in the PWA icon upload endpoint that extracts user-supplied ZIP archives without proper symlink validation. Attackers with BUILDER role can craft a malicious ZIP with leaf symlink entries followed by duplicate file entries to write arbitrary files as root, enabling remote code execution.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-100682 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100682 is a high-severity path traversal vulnerability in budibase server, published on 26 Sep 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-100682 exists.

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

## Sources

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

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