dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-48128

MEDIUM · 5.1 CVSS v4.0 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 3.39.0, the executeQuery automation step in Budibase accepts a queryId from automation step inputs and passes it directly to the query execution controller without additional validation. When combined with a REST datasource configured to target internal infrastructure, this creates a server-side request forgery path where automation execution causes the Budibase server to make outbound HTTP requests to attacker-influenced destinations. The automation output then returns the response, potentially exposing internal service data. This vulnerability is fixed in 3.39.0.

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 prior to 3.39.0 have an SSRF vulnerability in the executeQuery automation step. The queryId parameter is passed directly to the query execution controller without validation. When a REST datasource targets internal infrastructure, attackers can influence the server to make HTTP requests to internal services and exfiltrate the response data through automation outputs.

MitigationUpgrade Budibase to version 3.39.0 or later to obtain the fix. Additionally, review and restrict REST datasource configurations to prevent targeting internal infrastructure.

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

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
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 installed Budibase version
    Check the Budibase version by accessing the admin console, checking the container/package metadata, or querying the /api/global/self endpoint if authenticated. Compare the version number to the affected range (prior to 3.39.0).
    Affected if The installed version is earlier than 3.39.0
  2. Identify REST datasources
    Navigate to the Datasources section in the Budibase admin panel or query the /api/datasources endpoint to list all configured datasources. Identify datasources with type REST or HTTP.
    Affected if Any REST or HTTP datasources exist in the environment
  3. Check if REST datasources target internal infrastructure
    Examine the configuration of each REST datasource. Look for target URLs pointing to internal IP addresses (127.0.0.1, 10.x.x.x, 192.168.x.x, 172.16-31.x.x), localhost, or internal hostname patterns (internal.*, *.local, etc.).
    Affected if A REST datasource has a target URL resolving to internal network addresses or localhost
  4. Check for executeQuery automation usage
    Review automation workflows in the Automations section. Identify any automation that uses the executeQuery action step. Check which datasource and queryId are referenced by these steps.
    Affected if An automation uses the executeQuery step with a REST datasource configured to target internal infrastructure

The environment is affected if Budibase version is prior to 3.39.0 AND a REST datasource targeting internal infrastructure is used within an executeQuery automation step.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Budibase to version 3.39.0 or later to obtain the fix. Additionally, review and restrict REST datasource configurations to prevent targeting internal infrastructure.

Recommended fix High confidence

3.39.0

  1. Identify the current Budibase installation version using the admin interface or CLI
  2. Stop the Budibase service to prevent active connections during upgrade
  3. Backup the Budibase database and configuration files
  4. Upgrade Budibase to version 3.39.0 by following the official upgrade documentation for your deployment method (Docker, Kubernetes, or npm)
  5. After upgrade completes, verify the new version is 3.39.0 or higher
  6. Restart the Budibase service
  7. Test the executeQuery automation step to confirm it functions correctly with the fix in place

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48128 — 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-48128 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