dbcve.org
BudibaseApplication

CVE-2026-31818

CRITICAL · 9.9 CVSS v3.1 Published 2026-04-03
Fix available
A fix is available. Upgrade to 3.33.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Budibase is an open-source low-code platform. Prior to version 3.33.4, a server-side request forgery (SSRF) vulnerability exists in Budibase's REST datasource connector. The platform's SSRF protection mechanism (IP blacklist) is rendered completely ineffective because the BLACKLIST_IPS environment variable is not set by default in any of the official deployment configurations. When this variable is empty, the blacklist function unconditionally returns false, allowing all requests through without restriction. This issue has been patched in version 3.33.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Budibase versions before 3.33.4 contain a critical SSRF vulnerability in the REST datasource connector where the IP blacklist protection mechanism fails completely because the BLACKLIST_IPS environment variable is unset by default in official deployments. When this variable is empty, the blacklist function unconditionally returns false, allowing all outbound requests without restriction and enabling attackers to make the server perform arbitrary requests to internal or external resources.

MitigationUpgrade Budibase to version 3.33.4 or later to apply the patch, and ensure BLACKLIST_IPS is properly configured in deployment configurations to enable IP-based request filtering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BudibaseApplication
Affected:< 3.33.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Budibase version
    Check the Budibase installation for its version number, typically found in package.json, docker image tags, or the Budibase admin console under settings or about information.
    Affected if The installed version is earlier than 3.33.4
  2. Verify REST datasource connector is in use
    Inspect the Budibase application for any data sources configured using the REST connector type. This can be done through the Budibase UI under the Data section, or by examining configuration files if access is available.
    Affected if The REST datasource connector is configured and active within the Budibase application
  3. Check BLACKLIST_IPS environment variable
    Inspect the environment variables for the Budibase deployment. Look for the BLACKLIST_IPS variable in the server configuration, docker-compose file, or environment config. Verify if it is set to a non-empty value containing IP ranges.
    Affected if The BLACKLIST_IPS environment variable is not set or is empty, meaning the IP blacklist protection is not enforced

Your environment is affected if you are running Budibase versions prior to 3.33.4, have configured REST datasource connectors, and the BLACKLIST_IPS environment variable is unset or empty, allowing unrestricted outbound requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.33.4 or later
Fixed in 3.33.4
Vendor patch github.com →
Interim mitigation

Upgrade Budibase to version 3.33.4 or later to apply the patch, and ensure BLACKLIST_IPS is properly configured in deployment configurations to enable IP-based request filtering.

Recommended fix High confidence

3.33.4

  1. Upgrade Budibase to version 3.33.4 or later to address the SSRF vulnerability
  2. After upgrading, verify that the REST datasource connector SSRF protection is functioning correctly
  3. For custom deployments, consider explicitly configuring the BLACKLIST_IPS environment variable as an additional defense-in-depth measure
Caveat Review the 3.33.4 release notes for any potential breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Budibase Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31818 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31818 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data