CVE-2026-27702 json
Budibase Vulnerable to Remote Code Execution via Unsafe eval() in View Filter Map Function (Budibase Cloud)
published 2026-02-25 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-8646 , GHSA-rvhr-26g4-p2r8
- cvss
- 9.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
Budibase is a low code platform for creating internal tools, workflows, and admin panels. Prior to version 3.30.4, an unsafe `eval()` vulnerability in Budibase's view filtering implementation allows any authenticated user (including free tier accounts) to execute arbitrary JavaScript code on the server. This vulnerability ONLY affects Budibase Cloud (SaaS) - self-hosted deployments use native CouchDB views and are not vulnerable. The vulnerability exists in `packages/server/src/db/inMemoryView.ts` where user-controlled view map functions are directly evaluated without sanitization. The primary impact comes from what lives inside the pod's environment: the `app-service` pod runs with secrets baked into its environment variables, including `INTERNAL_API_KEY`, `JWT_SECRET`, CouchDB admin credentials, AWS keys, and more. Using the extracted CouchDB credentials, we verified direct database access, enumerated all tenant databases, and confirmed that user records (email addresses) are readable. Version 3.30.4 contains a patch.
Patch / fix
- npm budibase 3.30.4
- budibase budibase 3.30.4
- github.com/Budibase/budibase@3486598 commit
- github.com/Budibase/budibase#18087 pull request
- github.com/Budibase/budibase/releases/tag/3.30.4 release
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 8 mo ago
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/Budibase/budibase/security/advisories/GHSA-rvhr-26g4-p2r8 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L |
| GitHub | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L |
| NVD | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | budibase | <3.30.4 |
3.30.4 |
Affected products
- Budibase budibase
Classification
References
-
github.com
/Budibase/budibase/pull/18087
web, issue-tracking
-
github.com
/Budibase/budibase/commit/348659810cf930dda5f669e782706594c547115d
web, patch
-
github.com
/Budibase/budibase/security/advisories/GHSA-rvhr-26g4-p2r8
web, exploit, vendor-advisory
-
github.com
/Budibase/budibase/releases/tag/3.30.4
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-27702
advisory
-
github.com
/Budibase/budibase
package
Sources
- CVE List CVE-2026-27702
- GitHub Advisory GHSA-rvhr-26g4-p2r8
- NVD CVE-2026-27702
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.