VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

budibase: vulnerability history, versions and safety

budibase is a package in the npm ecosystem. Vulert records 7 vulnerabilities for it across 23 releases, from Feb 2026 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded C1 H4 M2
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
7 in the last 12 months

Most recent disclosure 18 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all budibase vulnerabilities

Vulert verdict on budibase 0.0.31 i

Updated on 23 Oct 2026

Careful: 0.0.31 has 7 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 39/100
  • Security Unfixed issues
  • Maintenance Deprecated
  • Popularity Niche
  • Community Moderate

The registry marks the latest release as deprecated, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.0.31 — affected i
  • Vulnerabilities on record 7 over 1 year · 7 in the last year i
  • Latest disclosure 18 Jun 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 1 i
  • Stars 28,330 i
  • OpenSSF scorecard 5/10 i
  • Last release 78 months ago i
  • Licence AGPL-3.0-or-later i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for budibase, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.0.31 02 Apr 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.30 02 Apr 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.29 31 Mar 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.28 31 Mar 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.27 05 Mar 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.24 27 Feb 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.23 27 Feb 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.22 27 Feb 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.21 26 Feb 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.20 26 Feb 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.19 26 Feb 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.18 26 Feb 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.17 26 Feb 2020 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.15 12 Nov 2019 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.14 09 Nov 2019 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.13 05 Nov 2019 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.12 19 Oct 2019 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.11 12 Oct 2019 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.10 12 Oct 2019 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.9 11 Oct 2019 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.8 11 Oct 2019 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.7 11 Oct 2019 C1 H4 M2 AGPL-3.0-or-later No Details →
0.0.3 10 Oct 2019 C1 H4 M2 AGPL-3.0-or-later No Details →

All 23 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 7

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 7 of the 7 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for budibase

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-27702: Budibase Remote Code Execution via Unsafe eval() in View Filter Map Function 9.9 critical 3.30.4 25 Feb 2026
CVE-2026-33226: Budibase Unrestricted SSRF Vulnerability via REST Datasource Query Preview 8.7 high No fix published 18 Mar 2026
Critical SQL Injection Vulnerabilities in Budibase Database Connectors 8.4 high 3.39.19 18 Jun 2026
CVE-2026-45061: Budibase SSRF Vulnerability via .tar.gz Substring Bypass in Plugin URL Upload 7.7 high 3.35.10 11 May 2026
CVE-2026-46426: Budibase Unrestricted File Upload Vulnerability Leading to Persistent XSS 7.6 high 3.38.2 19 May 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About budibase

Is budibase safe to use?

Vulert records 7 vulnerabilities for budibase in npm: 1 critical, 4 high, 2 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is budibase's Vulert package health score?

Vulert scores budibase 39/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of budibase affected?

Yes. 0.0.31, the version you would install today, has 7 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does budibase have?

7 vulnerabilities are recorded for budibase in the npm ecosystem: 1 critical, 4 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new budibase vulnerabilities disclosed?

7 vulnerabilities were recorded for budibase in the last 12 months, and the oldest entry in this database dates to 25 Feb 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of budibase are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor budibase for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the budibase version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.